From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 29383 invoked by alias); 10 May 2002 16:55:20 -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 29364 invoked from network); 10 May 2002 16:55:19 -0000 Received: from unknown (HELO duracef.shout.net) (204.253.184.12) by sources.redhat.com with SMTP; 10 May 2002 16:55:19 -0000 Received: (from mec@localhost) by duracef.shout.net (8.11.6/8.11.6) id g4AGtIn01593; Fri, 10 May 2002 11:55:18 -0500 Date: Fri, 10 May 2002 09:55:00 -0000 From: Michael Elizabeth Chastain Message-Id: <200205101655.g4AGtIn01593@duracef.shout.net> To: gdb-patches@sources.redhat.com, jimb@redhat.com Subject: Re: RFA: don't xfail ptype test X-SW-Source: 2002-05/txt/msg00343.txt.bz2 This patch is returned for more work. Hmmm. I agree that this is a bug: (gdb) ptype &*"foo" type = char [4] I get that behavior in all of my configurations. The problem is simply converting XFAIL -> FAIL. That's correct, but it doesn't leave a good enough trail for people doing regression analysis. Could you please file a bug report and then add a comment to the test script with the bug ID number in it: # setup_kfail "gdb/1234" The bug report can say that this bug is also present in 5.2. I am willing to file the bug report this evening if you want me to do that part. Michael C