[prev in list] [next in list] [prev in thread] [next in thread]
List: gdb
Subject: Re: MI and the prompt
From: Robert Rossi <bob () brasko ! net>
Date: 2021-01-29 2:40:47
Message-ID: CA+L9Jki=t0t9zhyB3X4Uh87dmN_ArxRAzQGMjEoSx37JPKOROg () mail ! gmail ! com
[Download RAW message or body]
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 in list] [next in list] [prev in thread] [next in thread]
Configure |
About |
News |
Add a list |
Sponsored by KoreLogic