From: Nick Roberts <nickrob@snap.net.nz>
To: "Stefan Burström" <f94sbu@efd.lth.se>
Cc: gdb@sources.redhat.com
Subject: -break-list output format
Date: Thu, 20 Oct 2005 11:15:00 -0000 [thread overview]
Message-ID: <17239.31877.235072.734864@kahikatea.snap.net.nz> (raw)
In-Reply-To: <344b46582c8.359607ed@mail.m.bonet.se>
[-- Warning: decoded text below may be mangled, UTF-8 assumed --]
[-- Attachment #1: Type: text/plain; charset=unknown, Size: 349 bytes --]
Stefan Burström writes:
> Hello!
> I am wondering why the output format of -break-list is rather different from
> the rest of the mi commands. Is there anything specific that I need to take
> care of when I parse the output?
What version of GDB are you running?
How is it different?
What do you want to do with the output?
Nick
next prev parent reply other threads:[~2005-10-20 11:15 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-09-07 14:23 MI parser Vladimir Prus
2005-09-07 14:29 ` Daniel Jacobowitz
2005-09-07 14:40 ` Bob Rossi
2005-10-20 11:08 ` -break-list output format Stefan Burström
2005-10-20 11:15 ` Nick Roberts [this message]
2005-10-20 11:27 ` Stefan Burström
2005-10-20 11:50 ` 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=17239.31877.235072.734864@kahikatea.snap.net.nz \
--to=nickrob@snap.net.nz \
--cc=f94sbu@efd.lth.se \
--cc=gdb@sources.redhat.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).