From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 11859 invoked by alias); 5 Apr 2008 16:56:28 -0000 Received: (qmail 11851 invoked by uid 22791); 5 Apr 2008 16:56:28 -0000 X-Spam-Check-By: sourceware.org Received: from main.gmane.org (HELO ciao.gmane.org) (80.91.229.2) by sourceware.org (qpsmtpd/0.31) with ESMTP; Sat, 05 Apr 2008 16:56:08 +0000 Received: from list by ciao.gmane.org with local (Exim 4.43) id 1JiBgO-0003Yn-Il for gdb@sources.redhat.com; Sat, 05 Apr 2008 16:56:00 +0000 Received: from 78.158.192.230 ([78.158.192.230]) by main.gmane.org with esmtp (Gmexim 0.1 (Debian)) id 1AlnuQ-0007hv-00 for ; Sat, 05 Apr 2008 16:56:00 +0000 Received: from ghost by 78.158.192.230 with local (Gmexim 0.1 (Debian)) id 1AlnuQ-0007hv-00 for ; Sat, 05 Apr 2008 16:56:00 +0000 To: gdb@sources.redhat.com From: Vladimir Prus Subject: Re: XFAIL vs. KFAIL Date: Sat, 05 Apr 2008 18:52:00 -0000 Message-ID: References: <200804051952.05563.vladimir@codesourcery.com> <20080405164927.GB16109@adacore.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7Bit User-Agent: KNode/0.10.5 X-IsSubscribed: yes Mailing-List: contact gdb-help@sourceware.org; run by ezmlm Precedence: bulk List-Id: List-Subscribe: List-Archive: List-Post: List-Help: , Sender: gdb-owner@sourceware.org X-SW-Source: 2008-04/txt/msg00052.txt.bz2 Joel Brobecker wrote: >> can somebody explain the difference between XFAILing and KFAILing a >> test in the GDB testsuite? I've looked at DejaGNU manual, I haven't >> found the answer. > > KFAIL is when we know of a failure caused by a bug in GDB. > > XFAIL is when a problem outside of GDB's control is causing the test > to fail. For instance, a kernel issue, or some wrong debugging info > generated by the compiler, etc. Hmm, it appears that at least MI testsuite routinely uses XFAIL for what is a GDB issue/limitation. Is the distinction really useful? Both seem to be a mechanism to "hide" failures that are known to be immediately fixeable, and exact description of the problem belongs to a comment, anyway. - Volodya