Mirror of the gdb mailing list
 help / color / mirror / Atom feed
From: Andrew Cagney <ac131313@cygnus.com>
To: Eli Zaretskii <eliz@is.elta.co.il>
Cc: jingham@apple.com, gdb@sources.redhat.com
Subject: Re: Questions about GDB-MI Interface`
Date: Fri, 26 Apr 2002 05:52:00 -0000	[thread overview]
Message-ID: <3CC94D6E.7080702@cygnus.com> (raw)
In-Reply-To: <6480-Fri26Apr2002105439+0300-eliz@is.elta.co.il>

> Date: Thu, 25 Apr 2002 12:23:17 -0700
>> From: Jim Ingham <jingham@apple.com>
>> 
>> So, we added an "-mi-interpreter-exec" command that runs commands as if it
>> were the console interpreter.  The syntax is:
>> 
>> mi-interpreter-exec console <command1> <command2> ...
>> 
>> These will feed the commands one by one to the execute_command function, AND
>> switch the output printer to the CLI printer, so you see console style
>> output.  Also, while the CLI command is running, it puts in place a series
>> of hooks that will report back interesting things to the GUI.
> 
> 
> Isn't it better to have the CLI-style output be followed by the
> MI-style output, with some clear separator between them?  The front
> end could then filter the CLI output to the display, while keeping
> the MI output for itself, to sync itself with the debugger.

I suspect the details would be like this.  There would also be a bit of 
pragmatism though.  To do this ``right'', GDB needs control over all 
output. That in turn means eliminating all those remaining printf's. 
Hmm, Pierre is quietly doing this!

enjoy,
Andrew


  reply	other threads:[~2002-04-26 12:52 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <1019760653.9107.ezmlm@sources.redhat.com>
2002-04-25 12:24 ` Jim Ingham
2002-04-26  0:55   ` Eli Zaretskii
2002-04-26  5:52     ` Andrew Cagney [this message]
2002-04-26  7:57     ` Jim Ingham
2002-04-26  8:21       ` Andrew Cagney
2002-04-26 10:10         ` Jim Ingham

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=3CC94D6E.7080702@cygnus.com \
    --to=ac131313@cygnus.com \
    --cc=eliz@is.elta.co.il \
    --cc=gdb@sources.redhat.com \
    --cc=jingham@apple.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