This is the mail archive of the
gdb-patches@sources.redhat.com
mailing list for the GDB project.
Re: Bug with lists in tables in ui-out.c
- From: Andrew Cagney <ac131313 at cygnus dot com>
- To: Andrew Cagney <ac131313 at cygnus dot com>
- Cc: Jim Ingham <jingham at apple dot com>,GDB Patches <gdb-patches at sources dot redhat dot com>
- Date: Wed, 05 Dec 2001 02:36:28 -0500
- Subject: Re: Bug with lists in tables in ui-out.c
- References: <B82AD27E.3211%jingham@apple.com> <3C0DC70E.6090607@cygnus.com>
> 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.
Thinking about this some more, I suspect you're constructing something like:
table={hdr={...},body=[{{<THIS>}, ...},...}]}
or as a code sequence:
..._body()
ui_out_tuple_begin(); /*row*/
ui_out_tupple_begin(); /* element - non-standard */
ui_out_field (...<THIS>..)
I'm wondering if a table is even applicable in this case. How exactly
should the header formatting information, for instance, be interpreted
when there is more than one entry.
Would you have an example?
Andrew