From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 7461 invoked by alias); 10 Jan 2002 18:06:07 -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 7362 invoked from network); 10 Jan 2002 18:06:04 -0000 Received: from unknown (HELO duracef.shout.net) (204.253.184.12) by sources.redhat.com with SMTP; 10 Jan 2002 18:06:04 -0000 Received: (from mec@localhost) by duracef.shout.net (8.8.7/8.8.7) id MAA25038; Thu, 10 Jan 2002 12:06:04 -0600 Date: Thu, 10 Jan 2002 10:06:00 -0000 From: Michael Elizabeth Chastain Message-Id: <200201101806.MAA25038@duracef.shout.net> To: msnyder@redhat.com Subject: Re: PATCH to testsuite/gdb.c++/namespace.exp Cc: gdb-patches@sources.redhat.com, jason@redhat.com X-SW-Source: 2002-01/txt/msg00237.txt.bz2 Michael Snyder wrote: > Would it not be better, then, if the test accepted both > \0 and \000? I thought about that. It would be better; and if I had written the patch, I would have written it that way. But there's so much to do in C++ land, and so little time, that I'd rather let it be. I'm 100x more worried about things like this: # native i686-pc-linux-gnu # gdb HEAD (2001-12-22) # gcc 2.95.3 # -gdwarf-2 print this^M $1 = (A * const) 0xa^M (gdb) PASS: gdb.c++/method.exp: print this (in foo) gdb is printing an incorrect value and the testsuite does not catch it. This is a bug in gdb and a shortfall in the testsuite and it affects real users. I am organizing my life so that I have more time to care about bugs like that. That means conserving attention on lesser things, to their detriment. It's an attention-triage question. But if this issue bothers you enough to submit a patch, I will approve it. Michael C