public inbox for gdb-prs@sourceware.org help / color / mirror / Atom feed
From: "cvs-commit at gcc dot gnu.org" <sourceware-bugzilla@sourceware.org> To: gdb-prs@sourceware.org Subject: [Bug threads/18600] After forking and threads spawning, gdb leaves newly created threads stopped Date: Thu, 06 Aug 2015 14:02:00 -0000 [thread overview] Message-ID: <bug-18600-4717-JxG9y1zzRU@http.sourceware.org/bugzilla/> (raw) In-Reply-To: <bug-18600-4717@http.sourceware.org/bugzilla/> https://sourceware.org/bugzilla/show_bug.cgi?id=18600 --- Comment #7 from cvs-commit at gcc dot gnu.org <cvs-commit at gcc dot gnu.org> --- The master branch has been updated by Pedro Alves <palves@sourceware.org>: https://sourceware.org/git/gitweb.cgi?p=binutils-gdb.git;h=f0ce0d3a331129309a46a6a9ac85fce35acae72b commit f0ce0d3a331129309a46a6a9ac85fce35acae72b Author: Pedro Alves <palves@redhat.com> Date: Thu Jul 23 16:01:01 2015 +0100 gdbserver: move_out_of_jump_pad_callback misses switching current thread While hacking on the fix for PR threads/18600 (Threads left stopped after fork+thread spawn), I once saw its test (fork-plus-threads.exp) FAIL against gdbserver because move_out_of_jump_pad_callback has a gdb_breakpoint_here call, and the caller isn't making sure the current thread points to the right thread. In the case I saw, the current thread pointed to the wrong process, so gdb_breakpoint_here returned the wrong answer. Unfortunately I didn't save logs. Still, seems obvious enough and it should fix a potential occasional racy FAIL. Tested on x86_64 Fedora 20. gdb/gdbserver/ChangeLog: 2015-08-06 Pedro Alves <palves@redhat.com> * linux-low.c (move_out_of_jump_pad_callback): Temporarily switch the current thread. -- You are receiving this mail because: You are on the CC list for the bug.
next prev parent reply other threads:[~2015-08-06 14:02 UTC|newest] Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top 2015-06-25 17:08 [Bug threads/18600] New: " simon.marchi at ericsson dot com 2015-06-25 17:08 ` [Bug threads/18600] " simon.marchi at ericsson dot com 2015-07-07 22:11 ` simon.marchi at ericsson dot com 2015-07-30 17:55 ` cvs-commit at gcc dot gnu.org 2015-07-30 17:55 ` cvs-commit at gcc dot gnu.org 2015-07-30 18:05 ` cvs-commit at gcc dot gnu.org 2015-07-30 18:05 ` cvs-commit at gcc dot gnu.org 2015-07-30 18:26 ` palves at redhat dot com 2015-08-06 14:02 ` cvs-commit at gcc dot gnu.org [this message] 2015-08-06 14:03 ` 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-18600-4717-JxG9y1zzRU@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).