From: David Carlton <carlton@math.stanford.edu>
To: Daniel Jacobowitz <drow@mvista.com>
Cc: Fernando Nasser <fnasser@redhat.com>, gdb-patches@sources.redhat.com
Subject: Re: [RFA/testsuite] Shorten the maint.exp symbols tests
Date: Wed, 04 Dec 2002 14:47:00 -0000 [thread overview]
Message-ID: <ro1smxd766f.fsf@jackfruit.Stanford.EDU> (raw)
In-Reply-To: <20021204222031.GA1112@nevyn.them.org>
On Wed, 4 Dec 2002 17:20:32 -0500, Daniel Jacobowitz <drow@mvista.com> said:
> 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.
It's certainly not obvious to me how to fix the testsuite in this
situation. After all, gdb_compile gets passed
${srcdir}/${subdir}/${srcfile}, which is exactly what you look for in
your maint print symbols call ("./gdb.base/break.c" in my example), so
I have a hard time imagining what a simple fix might be to the
testsuite that would allow it to guess the right thing (barring some
fragile hack like checking if $srcdir is ".").
> 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?
If it's easy to implement, one possibility would be for maint print
symbols to turn its argument into an absolute path (in a fairly
canonical form, so without ".", "..", and possibly without symbol
links) and to do the same thing for the filenames associated to the
symtabs before comparing those filenames to its argument.
David Carlton
carlton@math.stanford.edu
next prev parent reply other threads:[~2002-12-04 22:47 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-10-21 18:58 Daniel Jacobowitz
2002-12-03 7:19 ` Fernando Nasser
2002-12-04 13:52 ` David Carlton
2002-12-04 14:20 ` Daniel Jacobowitz
2002-12-04 14:47 ` David Carlton [this message]
2002-12-05 12:50 ` David Carlton
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=ro1smxd766f.fsf@jackfruit.Stanford.EDU \
--to=carlton@math.stanford.edu \
--cc=drow@mvista.com \
--cc=fnasser@redhat.com \
--cc=gdb-patches@sources.redhat.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox