This is the mail archive of the
gdb-prs@sourceware.org
mailing list for the GDB project.
[Bug threads/14618] scheduler-locking doesn't work with gdbserver
- From: "palves at redhat dot com" <sourceware-bugzilla at sourceware dot org>
- To: gdb-prs at sourceware dot org
- Date: Tue, 25 Sep 2012 11:42:03 +0000
- Subject: [Bug threads/14618] scheduler-locking doesn't work with gdbserver
- Auto-submitted: auto-generated
- References: <bug-14618-4717@http.sourceware.org/bugzilla/>
http://sourceware.org/bugzilla/show_bug.cgi?id=14618
Pedro Alves <palves at redhat dot com> changed:
What |Removed |Added
----------------------------------------------------------------------------
CC| |palves at redhat dot com
--- Comment #1 from Pedro Alves <palves at redhat dot com> 2012-09-25 11:42:03 UTC ---
scheduler-locking does work with gdbserver, otherwise schedlock.exp would fail.
... but only as long as the thread being debugged doesn't exit.
This is the "TARGET_WAITKIND_NO_RESUMED / graceful leader-exits" point in
http://sourceware.org/gdb/wiki/LocalRemoteFeatureParity
The GDB side fix (that added TARGET_WAITKIND_NO_RESUMED and those
testcases was <http://sourceware.org/ml/gdb-patches/2011-10/msg00704.html>.
When the (only) running thread exits, I think gdbserver ends up resuming the
whole inferior...
--
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.