From: Daniel Jacobowitz <drow@false.org>
To: "Nathan J. Williams" <nathanw@wasabisystems.com>,
gdb-patches@sources.redhat.com
Subject: Re: [patch] gdbserver: print correct child exit status/signal
Date: Fri, 19 Mar 2004 00:09:00 -0000 [thread overview]
Message-ID: <20040305034828.GG5320@nevyn.them.org> (raw)
In-Reply-To: <20040305030146.GC5320@nevyn.them.org>
On Thu, Mar 04, 2004 at 10:01:46PM -0500, Daniel Jacobowitz wrote:
> On Mon, Mar 01, 2004 at 04:15:18PM -0500, Nathan J. Williams wrote:
> >
> > Something else I had in my tree. Gdbserver was printing exit statuses
> > and termination signals from a variable that contained the in-protocol
> > signal from a command, if anything.
> >
> > - Nathan
> >
> > 2004-03-01 Nathan J. Williams <nathanw@wasabisystems.com>
> >
> > * server.c (main): Print child status or termination signal from
> > variable 'signal', not 'sig'.
>
> Fancy that, you're quite right. This is OK also.
Also committed to HEAD and 6.1.
--
Daniel Jacobowitz
MontaVista Software Debian GNU/Linux Developer
WARNING: multiple messages have this Message-ID
From: Daniel Jacobowitz <drow@false.org>
To: "Nathan J. Williams" <nathanw@wasabisystems.com>,
gdb-patches@sources.redhat.com
Subject: Re: [patch] gdbserver: print correct child exit status/signal
Date: Fri, 05 Mar 2004 03:48:00 -0000 [thread overview]
Message-ID: <20040305034828.GG5320@nevyn.them.org> (raw)
Message-ID: <20040305034800.QleCwd0AK0QxIoNgsV8gZRGRduGsJMgyYajfwwvYqic@z> (raw)
In-Reply-To: <20040305030146.GC5320@nevyn.them.org>
On Thu, Mar 04, 2004 at 10:01:46PM -0500, Daniel Jacobowitz wrote:
> On Mon, Mar 01, 2004 at 04:15:18PM -0500, Nathan J. Williams wrote:
> >
> > Something else I had in my tree. Gdbserver was printing exit statuses
> > and termination signals from a variable that contained the in-protocol
> > signal from a command, if anything.
> >
> > - Nathan
> >
> > 2004-03-01 Nathan J. Williams <nathanw@wasabisystems.com>
> >
> > * server.c (main): Print child status or termination signal from
> > variable 'signal', not 'sig'.
>
> Fancy that, you're quite right. This is OK also.
Also committed to HEAD and 6.1.
--
Daniel Jacobowitz
MontaVista Software Debian GNU/Linux Developer
next prev parent reply other threads:[~2004-03-05 3:48 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-03-19 0:09 Nathan J. Williams
2004-03-01 21:15 ` Nathan J. Williams
2004-03-05 3:01 ` Daniel Jacobowitz
2004-03-19 0:09 ` Daniel Jacobowitz
2004-03-19 0:09 ` Daniel Jacobowitz [this message]
2004-03-05 3:48 ` Daniel Jacobowitz
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=20040305034828.GG5320@nevyn.them.org \
--to=drow@false.org \
--cc=gdb-patches@sources.redhat.com \
--cc=nathanw@wasabisystems.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