On Tue, May 30, 2006 at 10:59:38AM -0700, Jim Ingham wrote:
On May 30, 2006, at 10:53 AM, Bob Rossi wrote:
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?
I'm not sure I like this. It doesn't really seem to mirror what's
going on. The -interpreter-exec command hasn't finished, rather,
it's asking - out of band - for some more information. So sending an
out-of-band message with this request seems cleaner. Why do you want
the extra (gdb) prompt?
Jim
I'm not sure what I asked for makes the most sense. However, I don't
really like what I see above.
Basically, up until now, the only time a front end would send data is
at the (gdb) prompt. That's when GDB is ready to except another
command.
This is also nice because if the FE generates a parser, it wants to
feed
that parser data until it spits out an MI output record. The parser
eventually spits out another MI outout record, the FE process's it,
and
then sends another command to GDB.
However, in the case above, the parser will keep eating data, and then
at some point, GDB will stop sending data and the MI output record has
not been completed. This means the parser will have to have some ugly
callback mechanism saying that the FE should send another command
to GDB.
What about something like this:
(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_oob_query)
I'm just brain storming here. What did you think of my rational?
Bob Rossi