From: Robert Rossi <bob@brasko.net>
To: GDB Development <gdb@sourceware.org>
Cc: Pedro Alves <palves@redhat.com>
Subject: Re: MI and the prompt
Date: Thu, 28 Jan 2021 21:40:47 -0500 [thread overview]
Message-ID: <CA+L9Jki=t0t9zhyB3X4Uh87dmN_ArxRAzQGMjEoSx37JPKOROg@mail.gmail.com> (raw)
In-Reply-To: <20210120033156.GA22914@xubuntu.brasko.net>
For the record, my testing shows that this issue does not occur when
using the 'new-ui mi' command line flag.
On Tue, Jan 19, 2021 at 10:31 PM Bob Rossi <bob@brasko.net> wrote:
> Hi,
>
> I long time ago I asked the GDB mailing list how to determine if GDB is
> ready
> for another command when using MI. Pedro Alves wrote:
>
> GDB is ready for input when it prints the MI prompt. There's one
> prompt that is already printed after ^running that you should ignore.
> That's an historical wart.
>
> I recently started to update cgdb to drop annotations and use the new-ui
> command line option. I noticed that i'm no longer seeing that historical
> wart.
>
> Has this been "fixed" in gdb? If so, is there a way to determine which
> versions of gdb have the historical wart, and which ones do not?
>
> Thanks,
> Bob Rossi
>
>
prev parent reply other threads:[~2021-01-29 2:40 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-01-20 3:31 Bob Rossi
2021-01-29 2:40 ` Robert Rossi [this message]
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='CA+L9Jki=t0t9zhyB3X4Uh87dmN_ArxRAzQGMjEoSx37JPKOROg@mail.gmail.com' \
--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).