Mirror of the gdb mailing list
 help / color / mirror / Atom feed
From: Eli Zaretskii <eliz@gnu.org>
To: Vladimir Prus <ghost@cs.msu.su>, gdb@sources.redhat.com
Subject: Re: MI -break-info command issues
Date: Tue, 24 Jan 2006 21:24:00 -0000	[thread overview]
Message-ID: <uk6cpfj0o.fsf@gnu.org> (raw)
In-Reply-To: <20060124144449.GE28357@brasko.net> (message from Bob Rossi on 	Tue, 24 Jan 2006 09:44:49 -0500)

> Date: Tue, 24 Jan 2006 09:44:49 -0500
> From: Bob Rossi <bob@brasko.net>
> Cc: gdb@sources.redhat.com
> 
> 2. The output of the command looks like this:
> > ^done,BreakpointTable={nr_rows="1",nr_cols="6",
> > hdr=[{width="3",alignment="-1",col_name="number",colhdr="Num"}
> > {width="14",alignment="-1",col_name="type",colhdr="Type"}
> > {width="4",alignment="-1",col_name="disp",colhdr="Disp"}
> > {width="3",alignment="-1",col_name="enabled",colhdr="Enb"}
> > {width="10",alignment="-1",col_name="addr",colhdr="Address"}
> > {width="40",alignment="2",col_name="what",colhdr="What"}],
> > body=[bkpt={number="2",type="breakpoint",disp="keep",enabled="y",
> > addr="0x08048464",func="main",file="main.cpp",line="6",times="1"}]}
> > 
> > What is the point of producing spreadsheet-like output with columns and
> > column heading and column alignment? I'd expect that any GUI frontend will
> > have some specific representation and just ignore that extra formatting.
> > Why generate it at all?
> 
> I agree, this output has always been useless to me. I would be happy to
> see it go away.

I DON'T agree, and I think it would be a grave mistake to have this
output go away.  About the worst thing a program can do is have some
information and not reveal it.  Skipping unneeded information is easy;
restoring missing one is next to impossible.


  parent reply	other threads:[~2006-01-24 21:21 UTC|newest]

Thread overview: 27+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-01-24 14:22 Vladimir Prus
2006-01-24 14:48 ` Bob Rossi
2006-01-24 15:02   ` Vladimir Prus
2006-01-24 21:24   ` Eli Zaretskii [this message]
2006-01-24 23:35     ` Bob Rossi
2006-01-25 16:05     ` Vladimir Prus
2006-01-25 19:42       ` Eli Zaretskii
2006-01-26 12:09         ` Vladimir Prus
2006-01-26 20:48           ` Eli Zaretskii
2006-01-27 12:16             ` Vladimir Prus
2006-01-27 14:55               ` Eli Zaretskii
2006-01-27 15:00                 ` Bob Rossi
2006-01-27 15:12                 ` Vladimir Prus
2006-01-27 15:48                   ` Daniel Jacobowitz
2006-01-27 15:51                     ` Vladimir Prus
2006-01-27 16:11                       ` Daniel Jacobowitz
2006-01-27 16:01                         ` Daniel Jacobowitz
2006-01-27 16:44                         ` Vladimir Prus
2006-01-27 17:00                           ` Bob Rossi
2006-02-10 12:03                             ` Documenting MI stability (Was: MI -break-info command issues) Vladimir Prus
2006-01-27 17:41                           ` MI -break-info command issues Eli Zaretskii
2006-01-27 17:16                       ` Eli Zaretskii
2006-01-27 17:53                         ` Bob Rossi
2006-01-28 14:48                           ` Eli Zaretskii
2006-01-27 17:12                   ` Eli Zaretskii
2006-03-17 17:07                     ` -data-read-memory docs (Was: MI -break-info command issues) Vladimir Prus
2006-03-18 11:26                       ` Eli Zaretskii

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=uk6cpfj0o.fsf@gnu.org \
    --to=eliz@gnu.org \
    --cc=gdb@sources.redhat.com \
    --cc=ghost@cs.msu.su \
    /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