From mboxrd@z Thu Jan  1 00:00:00 1970
Return-Path: <gdb-patches-return-14374-listarch-gdb-patches=sourceware.cygnus.com@sources.redhat.com>
Received: (qmail 15284 invoked by alias); 18 Apr 2002 16:06:41 -0000
Mailing-List: contact gdb-patches-help@sources.redhat.com; run by ezmlm
Precedence: bulk
List-Subscribe: <mailto:gdb-patches-subscribe@sources.redhat.com>
List-Archive: <http://sources.redhat.com/ml/gdb-patches/>
List-Post: <mailto:gdb-patches@sources.redhat.com>
List-Help: <mailto:gdb-patches-help@sources.redhat.com>, <http://sources.redhat.com/ml/#faqs>
Sender: gdb-patches-owner@sources.redhat.com
Received: (qmail 15243 invoked from network); 18 Apr 2002 16:06:37 -0000
Received: from unknown (HELO duracef.shout.net) (204.253.184.12)
  by sources.redhat.com with SMTP; 18 Apr 2002 16:06:37 -0000
Received: (from mec@localhost)
	by duracef.shout.net (8.11.6/8.11.6) id g3IG6U914843;
	Thu, 18 Apr 2002 11:06:30 -0500
Date: Thu, 18 Apr 2002 09:06:00 -0000
From: Michael Elizabeth Chastain <mec@shout.net>
Message-Id: <200204181606.g3IG6U914843@duracef.shout.net>
To: davem@redhat.com, fnasser@redhat.com
Subject: Re: [PATCH] Fix xfail Sparc pattern
Cc: cagney@cygnus.com, gdb-patches@sources.redhat.com
X-SW-Source: 2002-04/txt/msg00595.txt.bz2

Fernando Nasser writes:
> I wonder if we should activate this test and see where it fails and
> start marking as XFAILS (KFAILS actually) and entering a bug report 
> when we see the regressions.

I think so.  The comment indicates that this is due to a problem
inside gdb, not a problem with the environment, so that XFAIL is wrong
in the first place.

This is the old "XFAIL means an external program is not functional"
versus "XFAIL means that gdb is wrong but it's too painful to fix"
argument.

Michael C