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: Thu, 05 Dec 2002 12:50:00 -0000 [thread overview]
Message-ID: <ro1adjk42dj.fsf@jackfruit.Stanford.EDU> (raw)
In-Reply-To: <ro1smxd766f.fsf@jackfruit.Stanford.EDU>
On 04 Dec 2002 14:47:20 -0800, David Carlton <carlton@math.Stanford.EDU> said:
> On Wed, 4 Dec 2002 17:20:32 -0500, Daniel Jacobowitz <drow@mvista.com> said:
>> 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 ".").
I thought of another possible solution: maint.exp could copy
${srcdir}/${subdir}/${srcfile} to the current directory, then just
compile ${srcfile} without any path, and delete the stuff in the
current directory at the end of the tests. That's still not a great
solution, and I think probably the ultimate solution is to teach maint
print about canonical filenames, but it might work for now.
David Carlton
carlton@math.stanford.edu
prev parent reply other threads:[~2002-12-05 20:50 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
2002-12-05 12:50 ` David Carlton [this message]
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=ro1adjk42dj.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