From: Jim Ingham <jingham@apple.com>
To: Eli Zaretskii <eliz@is.elta.co.il>
Cc: GDB Patches <gdb-patches@sources.redhat.com>
Subject: Re: Bug with lists in tables in ui-out.c
Date: Mon, 03 Dec 2001 13:49:00 -0000 [thread overview]
Message-ID: <B8313361.356B%jingham@apple.com> (raw)
In-Reply-To: <Pine.SUN.3.91.1011129101958.10998L@is>
On 11/29/01 12:20 AM, "Eli Zaretskii" <eliz@is.elta.co.il> wrote:
>
> On Wed, 28 Nov 2001, Jim Ingham wrote:
>
>> Turns out if you have an element of a table that is a list or tuple, then
>> the current ui-out table code chokes. verify_field_alignment doesn't know
>> that each of the elements of the sublist are not separate table elements, so
>> it throws an error at the first one it sees. The following patch fixes this
>> bug.
>
> Jim, could you please skim over the documentation of UI_OUT functions
> in gdbint.texinfo and see if anything there needs to be updated due to
> this patch? For example, perhaps the warnings you put in comments
> should be repeated there.
>
> Thanks.
>
Eli,
I think the only thing that needs to be added is:
Index: gdbint.texinfo
===================================================================
RCS file: /cvs/Darwin/Commands/GNU/cygnus/src/gdb/doc/gdbint.texinfo,v
retrieving revision 1.12
diff -c -w -r1.12 gdbint.texinfo
*** gdbint.texinfo 2001/11/27 17:34:09 1.12
--- gdbint.texinfo 2001/12/03 21:46:39
***************
*** 860,867 ****
even when you are listing just one object but you still want the header.
@cindex nesting level in @code{ui_out} functions
! Tables can not be nested. Tuples and lists can be nested up to a
! maximum of five levels.
The overall structure of the table output code is something like this:
--- 860,867 ----
even when you are listing just one object but you still want the header.
@cindex nesting level in @code{ui_out} functions
! Tables can not be nested, nor can a tuple or list element be a table.
! Tuples and lists can be nested up to a maximum of five levels.
The overall structure of the table output code is something like this:
The other warnings are for writers of ui_out functions, not for their users,
and as such are not really appropriate in the gdbint doc, I think. With the
suggested patch, no behaviors change, things will now just work as expected.
Jim
--
+==+==+==+==+==+==+==+==+==+==+==+==+==+==+==+==+==+==+==
Jim Ingham jingham@apple.com
Developer Tools - gdb
next prev parent reply other threads:[~2001-12-03 21:49 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 [this message]
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
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=B8313361.356B%jingham@apple.com \
--to=jingham@apple.com \
--cc=eliz@is.elta.co.il \
--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