This is the mail archive of the
gdb-prs@sourceware.org
mailing list for the GDB project.
[Bug gdb/19828] 7.11 regression: non-stop gdb -p <process from a container>: internal error
- From: "cvs-commit at gcc dot gnu.org" <sourceware-bugzilla at sourceware dot org>
- To: gdb-prs at sourceware dot org
- Date: Tue, 24 May 2016 13:55:47 +0000
- Subject: [Bug gdb/19828] 7.11 regression: non-stop gdb -p <process from a container>: internal error
- Auto-submitted: auto-generated
- References: <bug-19828-4717 at http dot sourceware dot org/bugzilla/>
https://sourceware.org/bugzilla/show_bug.cgi?id=19828
--- 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=72b049d38ce85c51fc9f97ee64b00a47be5ebe94
commit 72b049d38ce85c51fc9f97ee64b00a47be5ebe94
Author: Pedro Alves <palves@redhat.com>
Date: Tue May 24 14:47:57 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-24 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.