From: Bob Rossi <bob@brasko.net>
To: Pedro Alves <palves@redhat.com>
Cc: GDB Development <gdb@sourceware.org>
Subject: Re: gdb/mi, new-ui. the console and determining when GDB is ready for the next command
Date: Sat, 11 Apr 2020 08:12:28 -0400 [thread overview]
Message-ID: <20200411121228.GA32166@xubuntu.brasko.net> (raw)
In-Reply-To: <e2e44a56-4bd6-e5f1-9201-a9fa45ac8ef0@redhat.com>
On Tue, Nov 05, 2019 at 02:06:30PM +0000, Pedro Alves wrote:
> On 11/2/19 10:35 AM, Robert Rossi wrote:
> > ...
> > =breakpoint-created,bkpt={number="1",type="breakpoint",...,original-location="main"}
> > <--- No GDB prompt
>
> A gdb prompt indicates that GDB is ready to accept commands
> again.
Sorry to respond to such an old thread. I'm just getting back into
this somehow.
The above statement surprises me. The MI manual describes an MI
output command with the following syntax,
output ->
( out-of-band-record )* [ result-record ] "(gdb)" nl
So I'm expecting "(gdb)\n" followed by the end of every output
command. Is this not how it works?
Thanks,
Bob Rossi
next prev parent reply other threads:[~2020-04-11 12:12 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-10-22 23:15 Robert Rossi
2019-10-25 9:58 ` Robert Rossi
2019-10-29 13:21 ` Pedro Alves
2019-11-02 10:35 ` Robert Rossi
2019-11-02 17:39 ` Jonah Graham
2019-11-05 14:06 ` Pedro Alves
2020-04-11 12:12 ` Bob Rossi [this message]
2020-04-11 14:09 ` Pedro Alves
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=20200411121228.GA32166@xubuntu.brasko.net \
--to=bob@brasko.net \
--cc=gdb@sourceware.org \
--cc=palves@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).