This is the mail archive of the
gdb-prs@sourceware.org
mailing list for the GDB project.
[Bug remote/18965] new vforkdone stop reply should indicate parent process ID
- From: "cvs-commit at gcc dot gnu.org" <sourceware-bugzilla at sourceware dot org>
- To: gdb-prs at sourceware dot org
- Date: Tue, 15 Sep 2015 18:37:30 +0000
- Subject: [Bug remote/18965] new vforkdone stop reply should indicate parent process ID
- Auto-submitted: auto-generated
- References: <bug-18965-4717 at http dot sourceware dot org/bugzilla/>
https://sourceware.org/bugzilla/show_bug.cgi?id=18965
--- Comment #6 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=9c53c9a4a221addc05c0cd3a8f44974d8c8b2444
commit 9c53c9a4a221addc05c0cd3a8f44974d8c8b2444
Author: Pedro Alves <palves@redhat.com>
Date: Tue Sep 15 19:35:56 2015 +0100
gdb/doc: revert previous vforkdone change
The previous manual change was wrong. The vfork parent thread ID
should be reported with the usual "thread" magic register:
Sending packet: $vCont;c:p7260.7260#1e...Packet received: OK
- Notification received: Stop:T05vforkdone:;
+ Notification received: Stop:T05vforkdone:;thread:p7260.7260
^^^^^^^^^^^^^^^^^
This is already how the parent is reported in the vfork/fork events,
and is actually what the fix made gdbserver do. Following the
documentation change, the event would have been reported like this
instead:
Notification received: Stop:T05vforkdone:p7260.7260
gdb/doc/ChangeLog:
2015-09-15 Pedro Alves <palves@redhat.com>
PR remote/18965
* gdb.texinfo (Stop Reply Packets): Revert previous change to
the vforkdone description.
--
You are receiving this mail because:
You are on the CC list for the bug.