This is the mail archive of the
gdb-prs@sourceware.org
mailing list for the GDB project.
[Bug threads/20291] Set scheduler-locking on doesn't work correctly with pthread_create
- From: "palves at redhat dot com" <sourceware-bugzilla at sourceware dot org>
- To: gdb-prs at sourceware dot org
- Date: Thu, 23 Jun 2016 09:11:45 +0000
- Subject: [Bug threads/20291] Set scheduler-locking on doesn't work correctly with pthread_create
- Auto-submitted: auto-generated
- References: <bug-20291-4717 at http dot sourceware dot org/bugzilla/>
https://sourceware.org/bugzilla/show_bug.cgi?id=20291
--- Comment #3 from Pedro Alves <palves at redhat dot com> ---
Note that nothing in gdb ever tried to make sure that "set scheduler-locking
on" locks new threads. Many targets can't even trap when a new thread is
created.
Actually, even when debugging against GNU/Linux gdbserver, even before that
patch, I believe you'll see the child running free, because gdbserver hasn't
been using libthread_db.so thread event breakpoints for a long while. Even
when it did, those thread event stops weren't reported to gdb, so the new
threads would still run free.
I think it was mainly working "by chance" before.
--
You are receiving this mail because:
You are on the CC list for the bug.