From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 14191 invoked by alias); 3 Dec 2002 16:54:43 -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 14126 invoked from network); 3 Dec 2002 16:54:42 -0000 Received: from unknown (HELO duracef.shout.net) (204.253.184.12) by sources.redhat.com with SMTP; 3 Dec 2002 16:54:42 -0000 Received: (from mec@localhost) by duracef.shout.net (8.11.6/8.11.6) id gB3GsZL31271; Tue, 3 Dec 2002 10:54:35 -0600 Date: Tue, 03 Dec 2002 08:54:00 -0000 From: Michael Elizabeth Chastain Message-Id: <200212031654.gB3GsZL31271@duracef.shout.net> To: drow@mvista.com, fnasser@redhat.com Subject: Re: [RFA/testsuite] Test printing complex numbers in C Cc: gdb-patches@sources.redhat.com X-SW-Source: 2002-12/txt/msg00073.txt.bz2 stabs DWARF-2 GCC 2.95 pass fail GCC 3.x fail pass Do gcc 2.95.3/dwarf-2 and gcc 3.x/stabs+ have identical output, or different output? If they are different output, you can do: send_gdb "blah" gdb_expect { -re "good output" { pass ... } -re "flaky gcc 2.95.3/dwarf-2 output" { setup_xfail_format "dwarf-2" fail ... } -re "flaky gcc 3.x/stabs+ output" { setup_xfail_format "stabs+" fail ... } -re ".*" { fail ... } } You can also dynamically poke at the executable to see what gcc compiled it. See "probe_demangler" in gdb.c++/cplusfuncs.exp for one way to do it. Michael C