[Bug threads/18600] After forking and threads spawning, gdb leaves newly created threads stopped

["cvs-commit at gcc dot gnu.org" <sourceware-bugzilla at sourceware dot org>]

https://sourceware.org/bugzilla/show_bug.cgi?id=18600

--- Comment #8 from cvs-commit at gcc dot gnu.org <cvs-commit at gcc dot gnu.org> ---
The gdb-7.10-branch branch has been updated by Pedro Alves
<palves@sourceware.org>:

https://sourceware.org/git/gitweb.cgi?p=binutils-gdb.git;h=a01c46276aa3a16c2ac1dae249df14e39d1c281f

commit a01c46276aa3a16c2ac1dae249df14e39d1c281f
Author: Pedro Alves <palves@redhat.com>
Date:   Thu Aug 6 15:02:26 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.