This is the mail archive of the
gdb-prs@sourceware.org
mailing list for the GDB project.
[Bug threads/10757] GDB does not attach all threads of a multithreaded process => inferior gets SIGTRAP
- From: "ppluzhnikov at google dot com" <sourceware-bugzilla at sourceware dot org>
- To: gdb-prs at sourceware dot org
- Date: 11 Oct 2009 23:27:46 -0000
- Subject: [Bug threads/10757] GDB does not attach all threads of a multithreaded process => inferior gets SIGTRAP
- References: <20091011171907.10757.ppluzhnikov@google.com>
- Reply-to: sourceware-bugzilla at sourceware dot org
------- Additional Comments From ppluzhnikov at google dot com 2009-10-11 23:27 -------
(In reply to comment #3)
> gdb/gdbserver/linux-low.c:linux_attach_lwp_1
> describes some races.
Please note that gdbserver is not involved in this bug report.
SIGTRAP is happening with 'gdb --pid' or '(gdb) attach'.
When using '(gdb) run' instead, everything works fine.
(In reply to comment #4)
> Also, if you let the app that crashed with a SIGTRAP dump
> core, you could load its core into gdb to check which breakpoint
> trapped
In all cores I've examined, it was the breakpoint on foo().
If I don't insert it, then I never get SIGTRAP.
--
http://sourceware.org/bugzilla/show_bug.cgi?id=10757
------- You are receiving this mail because: -------
You are on the CC list for the bug, or are watching someone who is.