This is the mail archive of the gdb@sourceware.org mailing list for the GDB project.


Index Nav: [Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav: [Date Prev] [Date Next] [Thread Prev] [Thread Next]
Other format: [Raw text]

Re: -break-list output format


> 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.

Well, I think it's a legacy issue. The table (with headers) has been
around for a long time. Long before MI was invented. So, I'm guessing
the writer of -break-list decided it would be good to keep that
information. You can ignore it if you choose.

Bob Rossi


Index Nav: [Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav: [Date Prev] [Date Next] [Thread Prev] [Thread Next]