Mirror of the gdb-patches mailing list
 help / color / mirror / Atom feed
From: "Carl E. Love" <cel@us.ibm.com>
To: Ulrich Weigand <uweigand@de.ibm.com>
Cc: Andreas Arnez <arnez@linux.vnet.ibm.com>,
	gdb-patches@sourceware.org,
	       Edjunior Barbosa Machado <emachado@linux.vnet.ibm.com>,
	       Ulrich Weigand <Ulrich.Weigand@de.ibm.com>
Subject: Re: [PATCH] Fix for gdb.server/non-existing-program.exp test case
Date: Tue, 13 Sep 2016 17:10:00 -0000	[thread overview]
Message-ID: <1473786588.4102.121.camel@us.ibm.com> (raw)
In-Reply-To: <20160913153701.960F411C2B7@oc8523832656.ibm.com>

On Tue, 2016-09-13 at 17:37 +0200, Ulrich Weigand wrote:
> Carl Love wrote:
> 
> > I fixed up the comment per your suggestion.  Not sure what happened with
> > the formatting. See if this looks better.
> 
> > +  /* The last_status.kind was set by the call to ptrace(PTRACE_TRACEME, ...).
> > +     The function linux_wait() has also been called.  At this point, the
> > +     target process, if it exits, is stopped.  Do not call the function
> > +     target_post_create_inferior if the process has already exited, as the
> > +     target implementation of the routine may rely on the process being live.
> > +  */
> 
> Formatting looks OK now, except that the trailing */ should not be on a
> separate line; see other multi-line comments how those should look like.
> 
> However, the comment still mentions ptrace and linux_wait, which is also
> only true on Linux targets.  I'd just leave that off.
> 
> Patch is OK with that change.
> 
> Bye,
> Ulrich
> 

Patch committed. Note, I updated the comment per requested.  Note, I
realized I only did part of the requested update initially and then did
then removed the ptrace () comment.  The patch didn't get updated with
the removal of the ptrace () comment.  I had to do a second commit to
get the ptrace () comment fixed correctly.  Sorry for the screw up.
Here are the two commits.


https://sourceware.org/git/gitweb.cgi?p=binutils-gdb.git;a=commit;h=1d8cb77dff14d44b1e3b670442438da496f99c6e
https://sourceware.org/git/gitweb.cgi?p=binutils-gdb.git;a=commit;h=7313bced5b695b71a707c82b6817763046e21bb1

                    Carl Love


      reply	other threads:[~2016-09-13 17:10 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-09-07 15:08 Carl E. Love
2016-09-13 13:26 ` Ulrich Weigand
2016-09-13 15:25   ` Carl E. Love
2016-09-13 15:37     ` Ulrich Weigand
2016-09-13 17:10       ` Carl E. Love [this message]

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=1473786588.4102.121.camel@us.ibm.com \
    --to=cel@us.ibm.com \
    --cc=Ulrich.Weigand@de.ibm.com \
    --cc=arnez@linux.vnet.ibm.com \
    --cc=emachado@linux.vnet.ibm.com \
    --cc=gdb-patches@sourceware.org \
    --cc=uweigand@de.ibm.com \
    /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: link
Be 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