This is the mail archive of the
gdb-patches@sources.redhat.com
mailing list for the GDB project.
Re: [RFA/testsuite] Shorten the maint.exp symbols tests
- From: Daniel Jacobowitz <drow at mvista dot com>
- To: David Carlton <carlton at math dot stanford dot edu>
- Cc: Fernando Nasser <fnasser at redhat dot com>, gdb-patches at sources dot redhat dot com
- Date: Wed, 4 Dec 2002 17:20:32 -0500
- Subject: Re: [RFA/testsuite] Shorten the maint.exp symbols tests
- References: <20021022015852.GA22669@nevyn.them.org> <3DECCDD4.1090808@redhat.com> <ro1wump78qj.fsf@jackfruit.Stanford.EDU>
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