Mirror of the gdb mailing list
 help / color / mirror / Atom feed
From: Tom Tromey <tom@tromey.com>
To: Bob Rossi <bob@brasko.net>
Cc: gdb@sourceware.org
Subject: Re: mi, new-ui and the target
Date: Mon, 06 May 2024 13:16:19 -0600	[thread overview]
Message-ID: <87v83qagzg.fsf@tromey.com> (raw)
In-Reply-To: <ZjaSoDwEd5SQ88K6@zelda> (Bob Rossi's message of "Sat, 4 May 2024 15:55:12 -0400")

>>>>> "Bob" == Bob Rossi <bob@brasko.net> writes:

Bob> My issue is as follows. When i try to take the target output specified
Bob> by @ and display it in the gdb window within cgdb, gdb decides to print
Bob> to stdout it's primpt (gdb), in the middle of the target output.
Bob> So I end up with the prompt randomely in the middle of the target
Bob> output and not at the end.

Bob> Is there any way to synchronize this text properly?

Bob> Please remember the point of the new-ui feature is to allow the user to
Bob> type the commands they want, and have the front end run the commands it
Bob> wants, in these should work together in a natural way.

This appears to be a bug in new-ui.

In particular, mi_interp::resume sets gdb_stdtarg but nothing ever
resets it in this scenario.

Could you file a bug report for this?

I don't know how this code is really supposed to work.
Maybe gdb_stdtarg* all have to be macros like gdb_stdout et al.

Or maybe some command executor somewhere should resume the tty's
interpreter before invoking the command.

I don't really understand the design of the ui/interpreter code.  To me
it seems a lot more convoluted than is really desirable or necessary.

Tom

  reply	other threads:[~2024-05-06 19:16 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-05-04 19:55 Bob Rossi
2024-05-06 19:16 ` Tom Tromey [this message]
2024-05-17 19:12   ` Tom Tromey

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=87v83qagzg.fsf@tromey.com \
    --to=tom@tromey.com \
    --cc=bob@brasko.net \
    --cc=gdb@sourceware.org \
    /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