From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 8225 invoked by alias); 3 Jan 2003 22:12: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 8216 invoked from network); 3 Jan 2003 22:12:41 -0000 Received: from unknown (HELO duracef.shout.net) (204.253.184.12) by 209.249.29.67 with SMTP; 3 Jan 2003 22:12:41 -0000 Received: (from mec@localhost) by duracef.shout.net (8.11.6/8.11.6) id h03MCQa20253; Fri, 3 Jan 2003 16:12:26 -0600 Date: Fri, 03 Jan 2003 22:12:00 -0000 From: Michael Elizabeth Chastain Message-Id: <200301032212.h03MCQa20253@duracef.shout.net> To: carlton@math.stanford.edu, drow@mvista.com Subject: Re: [patch/rfc] KFAIL gdb.c++/annota2.exp watch triggered on a.x Cc: gdb-patches@sources.redhat.com X-SW-Source: 2003-01/txt/msg00103.txt.bz2 One advantage of David's code is that when the bug gets fixed, people see a more informative message for a while: "KPASS gdb/38" rather than "PASS". One disadvantage is that it adds more file editing steps to the lifecycle. David, what edits, exactly, are you envisioning when "KPASS gdb/38" starts popping up? You shouldn't delete this part: -re "known bad expression" { kfail "gdb/NNN" "test name" } ... because old bugs have a way of popping up again, especially when additional configurations get tested. Michael C