This is the mail archive of the
gdb-prs@sourceware.org
mailing list for the GDB project.
[Bug gdb/10833] GDB crashes on debugging multithreaded program onARM SMP dual core system
- From: "pedro at codesourcery dot com" <sourceware-bugzilla at sourceware dot org>
- To: gdb-prs at sourceware dot org
- Date: Fri, 09 Sep 2011 10:56:36 +0000
- Subject: [Bug gdb/10833] GDB crashes on debugging multithreaded program onARM SMP dual core system
- Auto-submitted: auto-generated
- References: <bug-10833-4717@http.sourceware.org/bugzilla/>
http://sourceware.org/bugzilla/show_bug.cgi?id=10833
Pedro Alves <pedro at codesourcery dot com> changed:
What |Removed |Added
----------------------------------------------------------------------------
Status|NEW |WAITING
CC| |pedro at codesourcery dot
| |com
--- Comment #8 from Pedro Alves <pedro at codesourcery dot com> 2011-09-09 10:56:36 UTC ---
Please try with gdb 7.3, and paste the session so we can see the problem for
ourselves. From the older posts, it's not gdb that is crashing with SIGILL,
but
the program:
Program received signal SIGILL, Illegal instruction.
[Switching to Thread 1083503760 (LWP 351)]
0x4002639c in __nptl_death_event () from /lib/libpthread.so.0
Continuing from this resulted in a gdb internal error. I believe the latter
to be fixed nowadays.
The SIGILL could be explained by completely different problems, several not
really gdb's fault, but looks like something going wrong around the thread
death event breakpoint. Please show a session with both "set debug infrun 1"
and "set debug lin-lwp 1" issued before issuing "run". That will activate
gdb's run control debug messages and may help identify the problem.
--
Configure bugmail: http://sourceware.org/bugzilla/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are on the CC list for the bug.