public inbox for gdb-prs@sourceware.org help / color / mirror / Atom feed
From: "cvs-commit at gcc dot gnu.org" <sourceware-bugzilla@sourceware.org> To: gdb-prs@sourceware.org Subject: [Bug remote/18965] new vforkdone stop reply should indicate parent process ID Date: Tue, 15 Sep 2015 18:34:00 -0000 [thread overview] Message-ID: <bug-18965-4717-qBjDxY8WPc@http.sourceware.org/bugzilla/> (raw) In-Reply-To: <bug-18965-4717@http.sourceware.org/bugzilla/> https://sourceware.org/bugzilla/show_bug.cgi?id=18965 --- Comment #5 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=e68fa6f07666ec4726cfef59f641a81244cc2e00 commit e68fa6f07666ec4726cfef59f641a81244cc2e00 Author: Pedro Alves <palves@redhat.com> Date: Tue Sep 15 19:29:37 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.
next prev parent reply other threads:[~2015-09-15 18:34 UTC|newest] Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top 2015-09-15 16:10 [Bug remote/18965] New: " palves at redhat dot com 2015-09-15 16:10 ` [Bug remote/18965] " palves at redhat dot com 2015-09-15 16:33 ` cvs-commit at gcc dot gnu.org 2015-09-15 16:37 ` cvs-commit at gcc dot gnu.org 2015-09-15 17:03 ` cvs-commit at gcc dot gnu.org 2015-09-15 17:06 ` palves at redhat dot com 2015-09-15 18:34 ` cvs-commit at gcc dot gnu.org [this message] 2015-09-15 18:37 ` cvs-commit at gcc dot gnu.org 2021-10-21 6:50 ` bap.fayol at gmail dot com
Reply instructions: You may reply publicly to this message via plain-text email using any one of the following methods: * Save the following mbox file, import it into your mail client, and reply-to-all from there: mbox Avoid top-posting and favor interleaved quoting: https://en.wikipedia.org/wiki/Posting_style#Interleaved_style * Reply using the --to, --cc, and --in-reply-to switches of git-send-email(1): git send-email \ --in-reply-to=bug-18965-4717-qBjDxY8WPc@http.sourceware.org/bugzilla/ \ --to=sourceware-bugzilla@sourceware.org \ --cc=gdb-prs@sourceware.org \ /path/to/YOUR_REPLY https://kernel.org/pub/software/scm/git/docs/git-send-email.html * If your mail client supports setting the In-Reply-To header via mailto: links, try the mailto: linkBe sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions for how to clone and mirror all data and code used for this inbox; as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).