From: "Stefan Burström" <f94sbu@efd.lth.se>
To: gdb@sources.redhat.com
Subject: Re: -break-list output format
Date: Thu, 20 Oct 2005 11:27:00 -0000 [thread overview]
Message-ID: <344b4acc3d9.10ed0489@mail.m.bonet.se> (raw)
In-Reply-To: <17239.31877.235072.734864@kahikatea.snap.net.nz>
Hello Nick
On 2005-10-20, you wrote:
> What version of GDB are you running?
I am using 6.3
> How is it different?
Well, it includes a table header etc.If I want to build a table of the
output in my program I would of course just parse the output and build my
own tables with headers, labels etc.
For example, -file-list-exec-source-files just lists each file in a tuple.
But -break-list tells me the widh and height of the output etc. And I wonder
if I need to use it or if I can just skip the table header info. Finally, I
was just curious to know why the break-list output was done this way when
all other commands are more 'raw' in nature.
> What do you want to do with the output?
I am building a graphical frontend to gdb for AmigaOS4 :)
regards,
Stefan Burstrom
next prev parent reply other threads:[~2005-10-20 11:27 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
2005-10-20 11:27 ` Stefan Burström [this message]
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=344b4acc3d9.10ed0489@mail.m.bonet.se \
--to=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