From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 14574 invoked by alias); 4 Dec 2002 22:20:03 -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 14566 invoked from network); 4 Dec 2002 22:20:02 -0000 Received: from unknown (HELO crack.them.org) (65.125.64.184) by sources.redhat.com with SMTP; 4 Dec 2002 22:20:02 -0000 Received: from nevyn.them.org ([66.93.61.169] ident=mail) by crack.them.org with asmtp (Exim 3.12 #1 (Debian)) id 18Jjkg-0008Om-00; Wed, 04 Dec 2002 18:20:26 -0600 Received: from drow by nevyn.them.org with local (Exim 3.36 #1 (Debian)) id 18Jhse-0000Zy-00; Wed, 04 Dec 2002 17:20:32 -0500 Date: Wed, 04 Dec 2002 14:20:00 -0000 From: Daniel Jacobowitz To: David Carlton Cc: Fernando Nasser , gdb-patches@sources.redhat.com Subject: Re: [RFA/testsuite] Shorten the maint.exp symbols tests Message-ID: <20021204222031.GA1112@nevyn.them.org> Mail-Followup-To: David Carlton , Fernando Nasser , gdb-patches@sources.redhat.com References: <20021022015852.GA22669@nevyn.them.org> <3DECCDD4.1090808@redhat.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: User-Agent: Mutt/1.5.1i X-SW-Source: 2002-12/txt/msg00120.txt.bz2 On Wed, Dec 04, 2002 at 01:52:04PM -0800, David Carlton wrote: > The maint.exp changes in question cause testsuite failures on my > system for 'maint print symbols' and 'maint print psymbols'. I've > played around with it a bit; it seems to me that if I do > > (gdb) maint print symbols symbols_output ./gdb.base/break.c > > (which is what maint.exp does in my situation) then I get an empty > file symbols_output, whereas if I just do > > (gdb) maint print symbols symbols_output gdb.base/break.c > > then I get the correct symbols_output file. Here, I'm running GDB > from within the testsuite directory; I don't use a separate build > directory when configuring GDB, which might or might not make a > difference. Blech! I'm not sure what to do about this. Somehow we'd need to figure out how the file was compiled - is the logic to decide this in gdb_compile? Does the compiler clean it up on its own? Maybe if we pass an explicit srcdir to gdb_compile we can get consistent results here. Or maybe we should make 'maint print symbols symbols_output break.c' match all files ending in break.c. That's much less fragile. What do you think? -- Daniel Jacobowitz MontaVista Software Debian GNU/Linux Developer