From: Daniel Jacobowitz <drow@false.org>
To: Greg Law <glaw@level5networks.com>, gdb@sources.redhat.com
Subject: Re: Machine interface
Date: Fri, 18 Mar 2005 16:11:00 -0000 [thread overview]
Message-ID: <20050318161126.GA27141@nevyn.them.org> (raw)
In-Reply-To: <20050318160536.GA31080@white>
On Fri, Mar 18, 2005 at 11:05:36AM -0500, Bob Rossi wrote:
> On Fri, Mar 18, 2005 at 04:00:57PM +0000, Greg Law wrote:
> > Hi,
> >
> > I'm trying to find some info on GDB/MI. I've read the info pages. They
> > seem to be half finished, and specifically don't talk about one actually
> > interfaces with gdb/mi. ie. it doesn't seem to be via stdin of the gdb
> > processes (typing -break-point at it causes "unknown command" errors.
> > Do I need to open a socket to it or some such? Or do I just have the MI
> > syntax wrong?
>
> If you start GDB on the command line, you can use GDB the same way you
> use the CLI, of course with different syntax.
>
> The documentation for setting breakpoints in MI mode is here,
> http://sources.redhat.com/gdb/current/onlinedocs/gdb_25.html#SEC250
>
> in particular, try, '-break-insert main'
More specifically, Greg, I think you're missing the "-i=mi" option.
--
Daniel Jacobowitz
CodeSourcery, LLC
next prev parent reply other threads:[~2005-03-18 16:11 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-03-18 16:01 Greg Law
2005-03-18 16:05 ` Bob Rossi
2005-03-18 16:11 ` Daniel Jacobowitz [this message]
-- strict thread matches above, loose matches on Subject: below --
2003-06-03 22:09 Amusing problem in current libthread_db Daniel Jacobowitz
2003-06-03 22:30 ` Roland McGrath
2003-08-18 19:33 ` Daniel Jacobowitz
2003-08-19 6:45 ` Machine interface jacques
2003-08-19 13:30 ` Andrew Cagney
2003-08-19 14:00 ` Alain Magloire
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=20050318161126.GA27141@nevyn.them.org \
--to=drow@false.org \
--cc=gdb@sources.redhat.com \
--cc=glaw@level5networks.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;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).