diff options
| author | Pedro Alves <palves@redhat.com> | 2015-09-15 19:29:37 +0100 |
|---|---|---|
| committer | Pedro Alves <palves@redhat.com> | 2015-09-15 19:29:37 +0100 |
| commit | e68fa6f07666ec4726cfef59f641a81244cc2e00 (patch) | |
| tree | fac879fbd4a288071f9a117843aca0ca6f4f922a /gdb/symtab.h | |
| parent | b277c936e06479f38ec21dbd6322463c9435bad3 (diff) | |
| download | gdb-e68fa6f07666ec4726cfef59f641a81244cc2e00.zip gdb-e68fa6f07666ec4726cfef59f641a81244cc2e00.tar.gz gdb-e68fa6f07666ec4726cfef59f641a81244cc2e00.tar.bz2 | |
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.
Diffstat (limited to 'gdb/symtab.h')
0 files changed, 0 insertions, 0 deletions