From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 27747 invoked by alias); 5 Dec 2001 07:36:34 -0000 Mailing-List: contact gdb-patches-help@sources.redhat.com; run by ezmlm Precedence: bulk List-Subscribe: List-Archive: List-Post: List-Help: , Sender: gdb-patches-owner@sources.redhat.com Received: (qmail 27726 invoked from network); 5 Dec 2001 07:36:33 -0000 Received: from unknown (HELO localhost.cygnus.com) (24.114.42.213) by sources.redhat.com with SMTP; 5 Dec 2001 07:36:33 -0000 Received: from cygnus.com (localhost [127.0.0.1]) by localhost.cygnus.com (Postfix) with ESMTP id 6177B3E29; Wed, 5 Dec 2001 02:36:28 -0500 (EST) Message-ID: <3C0DCE7C.4090407@cygnus.com> Date: Tue, 04 Dec 2001 23:36:00 -0000 From: Andrew Cagney User-Agent: Mozilla/5.0 (X11; U; NetBSD macppc; en-US; rv:0.9.3) Gecko/20011020 X-Accept-Language: en-us MIME-Version: 1.0 To: Andrew Cagney Cc: Jim Ingham , GDB Patches Subject: Re: Bug with lists in tables in ui-out.c References: <3C0DC70E.6090607@cygnus.com> Content-Type: text/plain; charset=us-ascii; format=flowed Content-Transfer-Encoding: 7bit X-SW-Source: 2001-12/txt/msg00124.txt.bz2 > 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=[{{}, ...},...}]} or as a code sequence: ..._body() ui_out_tuple_begin(); /*row*/ ui_out_tupple_begin(); /* element - non-standard */ ui_out_field (.....) 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