From: Bob Rossi <bob_rossi@cox.net>
To: Nick Roberts <nickrob@snap.net.nz>, gdb-patches@sources.redhat.com
Subject: Re: starting gdb/mi from FE
Date: Tue, 06 Jun 2006 01:56:00 -0000 [thread overview]
Message-ID: <20060606015621.GF10045@brasko.net> (raw)
In-Reply-To: <20060606012001.GA7954@nevyn.them.org>
On Mon, Jun 05, 2006 at 09:20:02PM -0400, Daniel Jacobowitz wrote:
> On Tue, Jun 06, 2006 at 12:54:54PM +1200, Nick Roberts wrote:
> > I can't remember the previous outcome (I got lost with all the handshakes) but
> > I would prefer an MI command, -mi-version say, that the FE could use. It
> > could have a major and minor part: the major number to refer to the default MI
> > level; and the minor to help identify small changes made within one level. Of
> > course, we'd have to remember to update it, when appropriate.
> >
> > Pre GDB 6.5 wouldn't really work in this case either, but
> >
> > (gdb)
> > -mi-version
> > ^error,msg="Undefined MI command: mi-version"
> > (gdb)
> >
> > wouldn't require restarting GDB, while:
> >
> > nickrob/21 gdb -i=mi2,mi1 myprog
> > Interpreter `mi2,mi1' unrecognized
> > nickrob/22
> >
> > would.
>
> Two items.
>
> Nick, could you explain why the restart is a problem? The time GDB
> takes to reject an interpreter doesn't seem too bad. I don't want to
> optimize the wrong thing.
I would prefer not to restart GDB. I'm not so sure I agree with you that
the restart time is not a problem. I think it would be noticable on
older machines.
> Bob, since we last discussed this the interpreter commands have matured
> a bit. There's even tab completion for the CLI interpreter-exec
> command; try "interpreter-exec <tab>" and you'll get a list.
Yes, I see that now. My patch was causing GDB to crash when doing that.
I'll have to look more closely at the patch.
> Would -interpreter-list and -interpreter-set do it for you?
>
> I thought there already was a "set interp", but it seems I was
> mistaken.
Well, I'm not sure. My initial guess is no. Nick, please check this part
out also, especially in regards to your -mi-version command.
If GDB successfully starts with a -i=miN or just using the CLI and
hoping to switch to MI, then GDB is allowed to execute an arbitrary
number of commands before the FE can issue even a single command.
At least, in the CLI mode this is true if the user has commands in
.gdbinit.
I really can't afford to recieve a single MI output commadn before I
determine what generated parser I am going to use. So, I'll be stuck
starting GDB N times :(
Bob Rossi
next prev parent reply other threads:[~2006-06-06 1:56 UTC|newest]
Thread overview: 22+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-06-06 0:55 Nick Roberts
2006-06-06 1:20 ` Daniel Jacobowitz
2006-06-06 1:56 ` Bob Rossi [this message]
2006-06-06 3:16 ` Daniel Jacobowitz
2006-06-06 2:03 ` Nick Roberts
2006-06-06 2:04 ` Bob Rossi
2006-06-06 17:22 ` Jim Ingham
2006-06-06 17:30 ` Daniel Jacobowitz
2006-06-06 17:41 ` Jim Ingham
2006-06-06 1:33 ` Bob Rossi
2006-06-06 1:56 ` Nick Roberts
2006-06-06 2:01 ` Bob Rossi
2006-06-06 2:30 ` Nick Roberts
-- strict thread matches above, loose matches on Subject: below --
2006-06-05 13:45 Bob Rossi
2006-06-05 19:56 ` Eli Zaretskii
2006-06-05 19:58 ` Bob Rossi
2006-06-05 20:23 ` Eli Zaretskii
2006-06-05 21:25 ` Daniel Jacobowitz
2006-06-05 21:28 ` Bob Rossi
2006-06-06 3:44 ` Eli Zaretskii
2006-06-05 19:59 ` Daniel Jacobowitz
2006-06-05 20:49 ` Bob Rossi
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=20060606015621.GF10045@brasko.net \
--to=bob_rossi@cox.net \
--cc=gdb-patches@sources.redhat.com \
--cc=nickrob@snap.net.nz \
/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