From: Eli Zaretskii <eliz@gnu.org>
To: Andrew STUBBS <andrew.stubbs@st.com>
Cc: gdb@sources.redhat.com
Subject: Re: RFC: GDB as a loader 2/3: return child result
Date: Fri, 28 Oct 2005 12:58:00 -0000 [thread overview]
Message-ID: <u8xwder3a.fsf@gnu.org> (raw)
In-Reply-To: <436205A6.9010403@st.com> (message from Andrew STUBBS on Fri, 28 Oct 2005 12:04:06 +0100)
> Date: Fri, 28 Oct 2005 12:04:06 +0100
> From: Andrew STUBBS <andrew.stubbs@st.com>
>
> Here is a documentation patch to go with the original patch.
Thanks. My comments are below.
> +The return code from @value{GDBN} will be the return code from the child
> +process (the process being debugged), unless an error occurs or the user
> +quits with an explicit value, such as @samp{quit 1}, for example.
The "error occurs" part is not clear enough, IMO. Could you please
state more clearly what kinds of error could cause this ``unless''
clause to kick in? Also, if such an error does occur, what will GDB
return as its exit status in that case?
I think we should spell out all this information, since this option is
meant to be used by people who write shell scripts that invoke GDB in
batch mode. If I'd need to write such a script, I'd wish to know
exactly what kinds of exit codes I will see and under what
circumstances.
Otherwise, this patch is fine with me.
next prev parent reply other threads:[~2005-10-28 12:58 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-10-18 11:30 Andrew STUBBS
2005-10-28 11:06 ` Andrew STUBBS
2005-10-28 12:58 ` Eli Zaretskii [this message]
2005-10-28 14:01 ` Andrew STUBBS
2005-10-28 17:00 ` Eli Zaretskii
2005-11-03 11:57 ` Andrew STUBBS
2005-11-04 10:46 ` Eli Zaretskii
2005-11-04 11:52 ` Andrew STUBBS
2005-11-05 2:46 ` Daniel Jacobowitz
2005-11-07 12:20 ` Andrew STUBBS
2005-11-07 14:02 ` Daniel Jacobowitz
2005-11-07 14:40 ` Andrew STUBBS
2005-11-07 14:42 ` 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=u8xwder3a.fsf@gnu.org \
--to=eliz@gnu.org \
--cc=andrew.stubbs@st.com \
--cc=gdb@sources.redhat.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;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).