mi, new-ui and the target

Tom Tromey tom@tromey.com
Mon May 6 19:16:19 GMT 2024


>>>>> "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


More information about the Gdb mailing list