Re: [PATCH] PR/12691 Add the inferior to Python exited event

Eli Zaretskii
2011-09-01T10:08:11Z

> From: Kevin Pouget <kevin.pouget@gmail.com>
> Date: Thu, 1 Sep 2011 10:44:39 +0200
> Cc: Tom Tromey <tromey@redhat.com>, gdb-patches@sourceware.org
>
> On Wed, Aug 31, 2011 at 7:56 PM, Eli Zaretskii <eliz@gnu.org> wrote:
> >> From: Tom Tromey <tromey@redhat.com>
> >> Cc: Kevin Pouget <kevin.pouget@gmail.com>, gdb-patches@sourceware.org
> >> Date: Wed, 31 Aug 2011 11:53:21 -0600
> >>
> >> >>>>> "Eli" == Eli Zaretskii <eliz@gnu.org> writes:
> >>
> >> Eli> I'd still like to hear from someone "in the know" how is it possible
> >> Eli> that the exit code won't be available, but let's not block the commit
> >> Eli> on that behalf.
> >>
> >> It can happen at least on detach.
> >
> > Right, thanks. Â Perhaps we should mention that in parentheses.
> >
>
> do you want it to appear in my patch, something like
>
> > Optional, will exist only in the case that the inferior exited with some status---i.e., not detached)
>
> along with
>
> >> +An integer representing the exit code which the inferior has returned.
> > I think we would be better off without that "has" word.
>
> ?

No, I meant something like

An integer representing the exit code, if available, which the
inferior has returned. (The exit code could be unavailable if, for
example, @value{GDBN} detaches from the inferior.)