[Bug gdb/19828] 7.11 regression: non-stop gdb -p <process from a container>: internal error

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

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

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

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

commit a0de87e7be6a58dfeb9bfb00172dbd975dabb72e
Author: Pedro Alves <palves@redhat.com>
Date:   Wed May 25 18:35:09 2016 +0100

    Make gdb/linux-nat.c consider a waitstatus pending on the infrun side

    Working on the fix for gdb/19828, I saw
    gdb.threads/attach-many-short-lived-threads.exp fail once in an
    unusual way.  Unfortunately I didn't keep debug logs, but it's an
    issue similar to what's been fixed in remote.c a while ago --
    linux-nat.c was not fetching the pending status from the right place.

    gdb/ChangeLog:
    2016-05-25  Pedro Alves  <palves@redhat.com>

        PR gdb/19828
        * linux-nat.c (get_pending_status): If the thread reported the
        event to the core and it's pending, use the pending status signal
        number.

-- 
You are receiving this mail because:
You are on the CC list for the bug.