public inbox for gdb-prs@sourceware.org help / color / mirror / Atom feed
From: "palves at redhat dot com" <sourceware-bugzilla@sourceware.org> To: gdb-prs@sourceware.org Subject: [Bug threads/14618] scheduler-locking doesn't work with gdbserver Date: Tue, 25 Sep 2012 11:42:00 -0000 [thread overview] Message-ID: <bug-14618-4717-ZYvlXWpqwb@http.sourceware.org/bugzilla/> (raw) In-Reply-To: <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.
next prev parent reply other threads:[~2012-09-25 11:42 UTC|newest] Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top 2012-09-25 9:18 [Bug threads/14618] New: " tom.tan at analog dot com 2012-09-25 9:19 ` [Bug threads/14618] " tom.tan at analog dot com 2012-09-25 11:42 ` palves at redhat dot com [this message] 2012-09-26 7:58 ` [Bug threads/14618] gdbserver also exits after a thread exits if "set scheduler-locking on" tom.tan at analog dot com 2012-09-26 17:14 ` palves at redhat dot com 2012-09-26 17:18 ` [Bug threads/14618] gdbserver, scheduler-locking, thread exits and TARGET_WAITKIND_NO_RESUMED palves at redhat dot com 2014-02-27 15:11 ` palves at redhat dot com 2015-04-02 12:53 ` cvs-commit at gcc dot gnu.org
Reply instructions: You may reply publicly to this message via plain-text email using any one of the following methods: * Save the following mbox file, import it into your mail client, and reply-to-all from there: mbox Avoid top-posting and favor interleaved quoting: https://en.wikipedia.org/wiki/Posting_style#Interleaved_style * Reply using the --to, --cc, and --in-reply-to switches of git-send-email(1): git send-email \ --in-reply-to=bug-14618-4717-ZYvlXWpqwb@http.sourceware.org/bugzilla/ \ --to=sourceware-bugzilla@sourceware.org \ --cc=gdb-prs@sourceware.org \ /path/to/YOUR_REPLY https://kernel.org/pub/software/scm/git/docs/git-send-email.html * If your mail client supports setting the In-Reply-To header via mailto: links, try the mailto: linkBe sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions for how to clone and mirror all data and code used for this inbox; as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).