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.
This commit is contained in:
Pedro Alves 2015-09-15 19:29:37 +01:00
parent b277c936e0
commit e68fa6f076
2 changed files with 11 additions and 6 deletions

View File

@ -1,3 +1,9 @@
2015-09-15 Pedro Alves <palves@redhat.com>
PR remote/18965
* gdb.texinfo (Stop Reply Packets): Revert previous change to
the vforkdone description.
2015-09-15 Pedro Alves <palves@redhat.com>
PR remote/18965

View File

@ -35498,12 +35498,11 @@ indicating support.
@cindex vforkdone events, remote reply
@item vforkdone
The packet indicates that a child process created by a vfork has
either called @code{exec} or terminated, so that the address spaces of
the parent and child process are no longer shared. The @var{r} part
is the thread ID of the parent process. Refer to @ref{thread-id
syntax} for the format of the @var{thread-id} field. This packet is
only applicable to targets that support vforkdone events.
The packet indicates that a child process created by a vfork
has either called @code{exec} or terminated, so that the
address spaces of the parent and child process are no longer
shared. The @var{r} part is ignored. This packet is only
applicable to targets that support vforkdone events.
This packet should not be sent by default; older @value{GDBN} versions
did not support it. @value{GDBN} requests it, by supplying an