From: "Eli Zaretskii" <eliz@gnu.org>
To: gdb-patches@sources.redhat.com
Subject: Re: [mi] organize possible exec async mi oc command reasons
Date: Sat, 26 Mar 2005 13:32:00 -0000 [thread overview]
Message-ID: <01c53207$Blat.v2.4$edd75800@zahav.net.il> (raw)
In-Reply-To: <01c531ef$Blat.v2.4$d2dbeba0@zahav.net.il> (eliz@gnu.org)
> Date: Sat, 26 Mar 2005 12:36:32 +0200
> From: "Eli Zaretskii" <eliz@gnu.org>
>
> Btw, do we always have @var{reason} after "stopped"? If not, then
> it's optional and should be inside [...].
In addition, it looks to me like "stopped" states the reason like so:
*stopped,reason="REASON"
If this is true, then the first @table in the section we are talking
about should say
@table @code
@item
*stopped,reason="@var{reason}"
@end table
next prev parent reply other threads:[~2005-03-26 13:32 UTC|newest]
Thread overview: 29+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-03-24 15:46 Bob Rossi
2005-03-24 15:54 ` Daniel Jacobowitz
2005-03-24 16:06 ` Daniel Jacobowitz
2005-03-24 18:47 ` Stan Shebs
2005-03-24 21:20 ` Bob Rossi
2005-03-26 10:43 ` Eli Zaretskii
2005-04-30 19:32 ` Daniel Jacobowitz
2005-05-18 3:29 ` Bob Rossi
2005-05-18 3:34 ` Daniel Jacobowitz
2005-05-18 3:36 ` Bob Rossi
2005-05-18 3:43 ` Daniel Jacobowitz
2005-05-18 4:00 ` Bob Rossi
2005-05-18 8:53 ` Bob Rossi
2005-05-26 2:35 ` Bob Rossi
2005-05-28 18:56 ` Daniel Jacobowitz
2005-05-29 2:55 ` Bob Rossi
2005-05-29 3:00 ` Bob Rossi
2005-05-29 4:57 ` Daniel Jacobowitz
2005-05-29 5:53 ` Bob Rossi
2005-05-29 3:11 ` Daniel Jacobowitz
2005-06-15 19:25 ` David Lecomber
2005-06-15 20:03 ` Bob Rossi
2005-06-15 20:46 ` Daniel Jacobowitz
2005-03-24 20:00 ` Eli Zaretskii
2005-03-24 21:02 ` Bob Rossi
2005-03-26 10:40 ` Eli Zaretskii
2005-03-26 13:32 ` Eli Zaretskii [this message]
2005-03-27 2:56 ` Bob Rossi
2005-03-27 4:42 ` Eli Zaretskii
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='01c53207$Blat.v2.4$edd75800@zahav.net.il' \
--to=eliz@gnu.org \
--cc=gdb-patches@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