Mirror of the gdb-patches mailing list
 help / color / mirror / Atom feed
From: Daniel Jacobowitz <drow@false.org>
To: Nick Roberts <nickrob@snap.net.nz>, gdb-patches@sources.redhat.com
Subject: Re: starting gdb/mi from FE
Date: Tue, 06 Jun 2006 03:16:00 -0000	[thread overview]
Message-ID: <20060606031640.GA10701@nevyn.them.org> (raw)
In-Reply-To: <20060606015621.GF10045@brasko.net>

On Mon, Jun 05, 2006 at 09:56:21PM -0400, Bob Rossi wrote:
> > 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 :(

To avoid .gdbinit, start gdb with -nx.  If you want, then source
.gdbinit or $HOME/.gdbinit yourself.  You'll have to duplicate the
search for gdbinit files, but it's not as if that's a big deal.

As for whether you can parse the response of -interpreter-list, I don't
think there's any point in planning for that sort of drastic change to
the protocol.  We're talking about selecting a version of MI; all
versions of MI are supposed to follow more or less the same formats.

-- 
Daniel Jacobowitz
CodeSourcery


  reply	other threads:[~2006-06-06  3:16 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
2006-06-06  3:16     ` Daniel Jacobowitz [this message]
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=20060606031640.GA10701@nevyn.them.org \
    --to=drow@false.org \
    --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