This is the mail archive of the
glibc-bugs@sourceware.org
mailing list for the glibc project.
[Bug nptl/2697] New: NPTL can issue multiple simultaneous thread creation events
- From: "drow at sources dot redhat dot com" <sourceware-bugzilla at sourceware dot org>
- To: glibc-bugs at sources dot redhat dot com
- Date: 24 May 2006 20:23:12 -0000
- Subject: [Bug nptl/2697] New: NPTL can issue multiple simultaneous thread creation events
- Reply-to: sourceware-bugzilla at sourceware dot org
This seems like a feature, but in fact it isn't very useful, and complicates
debugging. GDB is not affected, because it uses a slower technique. However,
this breaks gdbserver. Because multiple threads could hit the thread creation
breakpoint simultaneously, gdbserver would have to stop all threads in order to
remove the breakpoint after any thread hit it. If other threads serialized and
waited for the previous event to be acknowledged, then gdbserver would not need
the extra overhead of stopping and resuming threads.
My proposed change, which only affects NPTL behavior when debugging events are
enabled, is here:
http://sourceware.org/ml/libc-alpha/2006-03/msg00104.html
--
Summary: NPTL can issue multiple simultaneous thread creation
events
Product: glibc
Version: 2.4
Status: NEW
Severity: normal
Priority: P2
Component: nptl
AssignedTo: drepper at redhat dot com
ReportedBy: drow at sources dot redhat dot com
CC: glibc-bugs at sources dot redhat dot com
http://sourceware.org/bugzilla/show_bug.cgi?id=2697
------- You are receiving this mail because: -------
You are on the CC list for the bug, or are watching someone who is.