From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 9324 invoked by alias); 19 Dec 2002 05:48:03 -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 9300 invoked from network); 19 Dec 2002 05:48:02 -0000 Received: from unknown (HELO duracef.shout.net) (204.253.184.12) by 209.249.29.67 with SMTP; 19 Dec 2002 05:48:02 -0000 Received: (from mec@localhost) by duracef.shout.net (8.11.6/8.11.6) id gBJ5lnN24237; Wed, 18 Dec 2002 23:47:49 -0600 Date: Thu, 19 Dec 2002 07:42:00 -0000 From: Michael Elizabeth Chastain Message-Id: <200212190547.gBJ5lnN24237@duracef.shout.net> To: carlton@math.stanford.edu, gdb-patches@sources.redhat.com Subject: Re: [patch] kfail gdb.c++/annota2.exp annotate-quit X-SW-Source: 2002-12/txt/msg00548.txt.bz2 My testbed gives me 34 KFAIL's on 34 configurations, just fine. This is native i686-pc-linux-gnu, gcc v2 and v3, dwarf-2 and stabs+. I use stock FSF dejagnu 1.4.3. I also built dejagnu from the sourcware cvs "dejagnu" module and did a test run with that. That works fine too. I have appended a gdb.sum file for anyone who is curious. The KFAIL line looks like this: KFAIL: gdb.c++/annota2.exp: annotate-quit (PRMS: c++/544) We can't do anything about the "PRMS:" part, that comes from dejagnu. I have an objection to the name "c++/544". It is way too easy for this name to get quoted out of context (the context being that it is a gdb bug in the gdb database). I think this will cause confusion. I would like to see "gdb/544" here. Sure, right *now* while we are discussing the issue, everyone knows that "c++/544" means a gdb bug in the gdb PR database. Wait six weeks and then quote some people a gdb.sum report that says "c++/482" in it and see if anyone jumps to the incorrect conclusion that c++/482 means a bug in the C++ compiler. Michael C === Test Run By mec on Thu Dec 19 00:20:19 2002 Native configuration is i686-pc-linux-gnu === gdb tests === Schedule of variations: unix/gdb:debug_flags=-gdwarf-2 Running target unix/gdb:debug_flags=-gdwarf-2 Running /berman/fsf/_today_/source/gdb/HEAD/src/gdb/testsuite/gdb.c++/annota2.exp ... PASS: gdb.c++/annota2.exp: breakpoint main PASS: gdb.c++/annota2.exp: annotation set at level 2 PASS: gdb.c++/annota2.exp: run until main breakpoint PASS: gdb.c++/annota2.exp: print class PASS: gdb.c++/annota2.exp: continue until exit PASS: gdb.c++/annota2.exp: delete bps PASS: gdb.c++/annota2.exp: breakpoint at main PASS: gdb.c++/annota2.exp: run until main breakpoint PASS: gdb.c++/annota2.exp: set watch on a.x FAIL: gdb.c++/annota2.exp: watch triggered on a.x KFAIL: gdb.c++/annota2.exp: annotate-quit (PRMS: c++/544) === gdb Summary === # of expected passes 9 # of unexpected failures 1 # of known failures 1 /berman/fsf/_today_/berman/native/install/gdb/HEAD/bin/gdb version 2002-12-12-cvs -nx