Mirror of the gdb mailing list
 help / color / mirror / Atom feed
From: Bob Rossi <bob_rossi@cox.net>
To: Jim Ingham <jingham@apple.com>
Cc: gdb@sources.redhat.com
Subject: Re: MI query questions
Date: Tue, 30 May 2006 17:55:00 -0000	[thread overview]
Message-ID: <20060530175310.GD31100@brasko.net> (raw)
In-Reply-To: <DD27DB7B-9CDD-4E98-85F5-FB33121A48E7@apple.com>

On Tue, May 30, 2006 at 10:48:53AM -0700, Jim Ingham wrote:
> Actually, to avoid confusion, this really looks like:
> 
> (gdb) set interpreter mi1
> -interpreter-exec console-quoted "break raise"
> ~"[0] cancel\n[1] all\n"
> ~"\nNon-debugging symbols:\n"
> ~"[2]    -[NSException raise]\n"
> ~"[3]    raise\n"
> =read-one-line,prompt="> "
> 
> In our version of gdb the console interpreter really is the straight  
> CLI console interpreter - this is required to get the "set  
> interpreter" command to work.  So we had to invent another  
> interpreter that did the proper quoting.  Anyway, this is what it  
> would look like for you...

This is also the solution I was thinking of. However, I would like to
modify the MI OUTPUT record to show this as a possibility. Also, I think
that this should be 1 full response.
    (gdb) set interpreter mi1
    -interpreter-exec console-quoted "break raise"
    ~"[0] cancel\n[1] all\n"
    ~"\nNon-debugging symbols:\n"
    ~"[2]    -[NSException raise]\n"
    ~"[3]    raise\n"
    =read-one-line,prompt="> "
    (gdb)

And then the user will send the command, and then get another full
response representing the breakpoint output.

Does this make sense?

This would mean that there would be a new part of the MI output record
that would tell the FE that it needs to ask the user for more
information. Most FE's that have used annotate 1 or 2 have already come
across this situation and dealt with it nicely.

Thanks,
Bob Rossi


  reply	other threads:[~2006-05-30 17:53 UTC|newest]

Thread overview: 22+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-05-30  3:48 Bob Rossi
2006-05-30  8:20 ` Daniel Jacobowitz
2006-05-30 17:15   ` Jim Ingham
2006-05-30 17:41     ` Bob Rossi
2006-05-30 17:53       ` Jim Ingham
2006-05-30 17:55         ` Jim Ingham
2006-05-30 17:55           ` Bob Rossi [this message]
2006-05-30 18:12             ` Daniel Jacobowitz
2006-05-30 20:14             ` Jim Ingham
2006-05-30 18:27               ` Bob Rossi
2006-05-30 18:56                 ` Jim Ingham
2006-05-30 20:46                   ` Bob Rossi
2006-05-30 21:11                     ` Jim Ingham
2006-05-30 21:15                       ` Daniel Jacobowitz
2006-05-30 21:30                         ` Jim Ingham
2006-05-31  9:38                           ` Daniel Jacobowitz
2006-05-31 13:27                             ` Bob Rossi
2006-05-30 17:00 ` Nick Roberts
2006-05-30 17:32   ` Bob Rossi
2006-05-31 10:29     ` Nick Roberts
2006-05-31 13:25       ` Bob Rossi
2006-06-01  0:58         ` Nick Roberts

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=20060530175310.GD31100@brasko.net \
    --to=bob_rossi@cox.net \
    --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