NetBSD-Bugs archive

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index][Old Index]

toolchain/54589: gdb is not working for core files on evbarm



>Number:         54589
>Category:       toolchain
>Synopsis:       gdb is not working for core files on evbarm
>Confidential:   no
>Severity:       serious
>Priority:       medium
>Responsible:    toolchain-manager
>State:          open
>Class:          sw-bug
>Submitter-Id:   net
>Arrival-Date:   Tue Oct 01 12:35:00 +0000 2019
>Originator:     Martin Husemann
>Release:        NetBSD 9.99.15
>Organization:
The NetBSD Foundation, Inc.
>Environment:
System: NetBSD unpluged.duskware.de 9.99.15 NetBSD 9.99.15 (UNPLUGED) #265: Tue Oct 1 13:38:00 CEST 2019 martin%seven-days-to-the-wolves.aprisoft.de@localhost:/work/src/sys/arch/evbarm/compile/UNPLUGED evbarm
Architecture: earm
Machine: evbarm
>Description:

Trying to debug a core dump on evbarm fails:

# gdb named named.core 
GNU gdb (GDB) 8.3
Copyright (C) 2019 Free Software Foundation, Inc.
License GPLv3+: GNU GPL version 3 or later <http://gnu.org/licenses/gpl.html>
This is free software: you are free to change and redistribute it.
There is NO WARRANTY, to the extent permitted by law.
Type "show copying" and "show warranty" for details.
This GDB was configured as "armv7--netbsdelf-eabihf".
Type "show configuration" for configuration details.
For bug reporting instructions, please see:
<http://www.gnu.org/software/gdb/bugs/>.
Find the GDB manual and other documentation resources online at:
    <http://www.gnu.org/software/gdb/documentation/>.

For help, type "help".
Type "apropos word" to search for commands related to "word"...
Reading symbols from named...
Reading symbols from /usr/libdata/debug//usr/sbin/named.debug...
[New process 1]
[New process 4]
[New process 3]
[New process 2]
Core was generated by `named'.
Program terminated with signal SIGBUS, Bus error.
#0  0xbbba0e84 in ?? ()
[Current thread is 1 (process 1)]
(gdb) bt
#0  0xbbba0e84 in ?? ()
#1  0xbbba0ad4 in ?? ()
Backtrace stopped: previous frame identical to this frame (corrupt stack?)
(gdb) x/16i $pc
=> 0xbbba0e84:  Register 25 is not available
(gdb) info reg
r0             0xbbbc71f4          3149689332
r1             0xbfffd950          3221215568
r2             0x1                 1
r3             0xbfffd948          3221215560
r4             0xbb2579f8          3139795448
r5             0xbfffd950          3221215568
r6             0x1                 1
r7             0x0                 0
r8             0xbb255a28          3139787304
r9             0xbb260a10          3139832336
r10            0xbbbca000          3149701120
r11            0xbfffdd6c          3221216620
r12            0xbbba0e80          3149532800
sp             0xbfffd928          0xbfffd928
lr             0xbbba0ad4          3149531860
pc             0xbbba0e84          0xbbba0e84
cpsr           <unavailable>
(gdb) x/i 0xbbba0e84
=> 0xbbba0e84:  Register 25 is not available
(gdb) x/i 0xbbba0e84
=> 0xbbba0e84:  Register 25 is not available
(gdb) info threads
  Id   Target Id         Frame 
* 1    process 1         0xbbba0e84 in ?? ()
  2    process 4         0xbb6fb098 in ?? ()
  3    process 3         0xbb6fbba0 in ?? ()
  4    process 2         0xbb6fbba0 in ?? ()

Note also the missing symbols (despite successfully loading them).

>How-To-Repeat:
s/a

>Fix:
n/a



Home | Main Index | Thread Index | Old Index