Mirror of the gdb mailing list
 help / color / mirror / Atom feed
From: Bob Rossi <bob@brasko.net>
To: gdb@sourceware.org
Subject: mi, new-ui and the target
Date: Sat, 4 May 2024 15:55:12 -0400	[thread overview]
Message-ID: <ZjaSoDwEd5SQ88K6@zelda> (raw)

Hi,

I maintain cgdb, a curses based front end to gdb.
I got a bug report here,
  https://github.com/cgdb/cgdb/issues/352
that i'm trying to resolve.

In one terminal i run
    valgrind --vgdb-error=0 ./main.

In another terminal i run
    gdb --ex "new-ui mi /dev/pts/12" --ex 'target remote | vgdb'
From a 3rd terminal i run 'tty' to get /dev/pts/12.

Now, when i run 'monitor help' from the gdb terminal, i get this:
    (gdb) monitor help
    (gdb) 
please note the second prompt displayed by gdb.

In the third terminal, represented by /dev/pts/12, i see the proper
valgrind output. For instance,
  @"general valgrind monitor commands:\n"
  ....
  @"\n"
please note, it does not end with a (gdb) prompt or with ^done.

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

Is there any way to synchronize this text properly?

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

Thanks,
Bob Rossi

             reply	other threads:[~2024-05-04 19:55 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-05-04 19:55 Bob Rossi [this message]
2024-05-06 19:16 ` Tom Tromey
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=ZjaSoDwEd5SQ88K6@zelda \
    --to=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