This is the mail archive of the gdb-prs@sourceware.org mailing list for the GDB project.


Index Nav: [Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav: [Date Prev] [Date Next] [Thread Prev] [Thread Next]
Other format: [Raw text]

[Bug gdb/10833] New: GDB crashes on debugging multithreaded program on ARM SMP dual core system


When running gdb on a multithreaded program on a dual core SMP system the 
program carshes with the error log as given below. The same program when run 
without gdb works fine.

root$ gdb hex
GNU gdb STMicroelectronics/Linux Base 6.6-15
Copyright (C) 2006 Free Software Foundation, Inc.
GDB is free software, covered by the GNU General Public License, and you are
welcome to change it and/or distribute copies of it under certain conditions.
Type "show copying" to see the conditions.
There is absolutely no warranty for GDB.  Type "show warranty" for details.
This GDB was configured as "arm-cortex-linux-gnueabi"...
Using host libthread_db library "/lib/libthread_db.so.1".
(gdb) run
Starting program: /opt/hex
[Thread debugging using libthread_db enabled]
[New Thread 1073848128 (LWP 348)]
[New Thread 1083503760 (LWP 351)]
[New Thread 1091892368 (LWP 352)]
348: Hello world [0]
0
348: Hello world [1]
348: Hello world [2]
348: Hello world [3]
348: Hello world [4]
348: Hello world [5]
348: Hello world [6]
348: Hello world [7]
348: Hello world [8]
348: Hello world [9]
348: Hello world [0]
[Thread 1083503760 (LWP 351) exited]

Program received signal SIGILL, Illegal instruction.
[Switching to Thread 1083503760 (LWP 351)]
0x4002639c in __nptl_death_event () from /lib/libpthread.so.0
(gdb) bt
#0  0x4002639c in __nptl_death_event () from /lib/libpthread.so.0
#1  0x40026d3c in start_thread () from /lib/libpthread.so.0
#2  0x400f1548 in clone () from /lib/libc.so.6
Backtrace stopped: frame did not save the PC
(gdb) c
Continuing.
../../gdb/linux-nat.c:2074: internal-error: linux_nat_wait: Assertion 
`iterate_over_lwps (running_ca
llback, NULL)' failed.
A problem internal to GDB has been detected,
further debugging may prove unreliable.
Quit this debugging session? (y or n) y

../../gdb/linux-nat.c:2074: internal-error: linux_nat_wait: Assertion 
`iterate_over_lwps (running_ca
llback, NULL)' failed.
A problem internal to GDB has been detected,
further debugging may prove unreliable.
Create a core file of GDB? (y or n) n
root$


GDB Version: 6.6
Platform: ARM CortexA9 Dual Core SMP
GLIBC - 2.6.1
GCC - 4.2.4
Kernel - 2.6.27
Configure options to GDB:
../configure --host=arm-cortex-linux-gnueabi --build=i686-pc-linux-gnu --
prefix=/usr --exec-prefix=/usr --bindir=/usr/bin --sbindir=/usr/sbin --
sysconfdir=/etc --datadir=/usr/share --includedir=/usr/include --
libdir=/usr/lib --libexecdir=/usr/libexec --localstatedir=/var --
sharedstatedir=/usr/share --mandir=/usr/share/man --infodir=/usr/share/info --
disable-gdbtk

The sample program which crashed repeatedly is attached.

-- 
           Summary: GDB crashes on debugging  multithreaded program on ARM
                    SMP dual core system
           Product: gdb
           Version: 6.6
            Status: UNCONFIRMED
          Severity: critical
          Priority: P2
         Component: gdb
        AssignedTo: unassigned at sourceware dot org
        ReportedBy: melwyn dot lobo at gmail dot com
                CC: gdb-prs at sourceware dot org


http://sourceware.org/bugzilla/show_bug.cgi?id=10833

------- You are receiving this mail because: -------
You are on the CC list for the bug, or are watching someone who is.


Index Nav: [Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav: [Date Prev] [Date Next] [Thread Prev] [Thread Next]