From: Jim Ingham <jingham@apple.com>
To: Andrew Cagney <ac131313@cygnus.com>
Cc: GDB Patches <gdb-patches@sources.redhat.com>
Subject: Re: Bug with lists in tables in ui-out.c
Date: Thu, 06 Dec 2001 16:41:00 -0000 [thread overview]
Message-ID: <B835503A.3341%jingham@apple.com> (raw)
In-Reply-To: <3C0FF9D9.4010607@cygnus.com>
On 12/6/01 3:06 PM, "Andrew Cagney" <ac131313@cygnus.com> wrote:
>
>> Andrew,
>>
>> The example is the table that "info break" makes. In FSF gdb, you only emit
>> table headers for the first 6 columns, and if there are commands, they are
>> added to the bkpt tuple (and so formally should be other columns in the
>> table), but there is no equivalent entry in the header list. The table code
>> doesn't require that all data in a table row have an equivalent header
>> entry, so this works, but this is just a bit bogus... Somebody here got
>> annoyed by this and added table headers for the other columns - mostly so
>> users could see what the columns mean. In this case, the list that is being
>> added to the table is the list of breakpoint commands.
>
> Ah, yes. Ok, got it (head butts table). I think I'll check it in
> slightly different though - add the code that advances the headings to
> the ..._begin() instead of ..._end() function. I think that will sit
> better with the other logic already handling tables.
>
> Make sense?
Sounds fine. If you are going to check this in, will you check the doc
patch too? Thanks.
Jim
--
++=++=++=++=++=++=++=++=++=++=++=++=++=++=++=++=++=++=++=
Jim Ingham jingham@apple.com
Developer Tools - gdb
next prev parent reply other threads:[~2001-12-07 0:41 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-11-28 17:42 Jim Ingham
2001-11-18 11:04 ` Jim Ingham
2001-11-29 0:20 ` Eli Zaretskii
2001-11-19 11:24 ` Eli Zaretskii
2001-12-03 13:49 ` Jim Ingham
2001-12-04 0:08 ` Eli Zaretskii
2001-12-04 23:05 ` Andrew Cagney
2001-12-04 23:36 ` Andrew Cagney
2001-12-05 11:59 ` Jim Ingham
2001-12-06 15:06 ` Andrew Cagney
2001-12-06 16:41 ` Jim Ingham [this message]
2001-12-07 11:01 ` Andrew Cagney
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=B835503A.3341%jingham@apple.com \
--to=jingham@apple.com \
--cc=ac131313@cygnus.com \
--cc=gdb-patches@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