From: Michael Chastain <mec.gnu@mindspring.com>
To: cagney@gnu.org
Cc: jimb@redhat.com, gdb@sources.redhat.com, ezannoni@redhat.com,
cagney@redhat.com
Subject: Re: gdb.mi/*.exp and absolute line numbers
Date: Fri, 06 Aug 2004 16:06:00 -0000 [thread overview]
Message-ID: <4113AC7D.nailD201292RT@mindspring.com> (raw)
In-Reply-To: <411399C4.9060108@gnu.org>
Andrew Cagney <cagney@gnu.org> wrote:
> (What happens with a soft-link or file copy (where the file name isn't
> in $srcdir) as is done with the asm tests).
This call would stop working:
[gdb_get_line_number "foo" arch.inc]
However this call would work fine:
[gdb_get_line_number "foo" ${asm-arch}.inc]
Fortunately there are no such calls in the corpus, so it won't hurt when
I change the semantics from "gdb looks for the file on the host machine"
to "tcl looks for the file on the build machine".
The test script always has to know the names of the files on the build
machine, in order to get them to the host machine in the first place.
Something like gdb.stabs/weird.exp would be more painful, because it
actually runs 'sed' on the *host* machine to preprocess files before
feeding them to gdb_compile. For something like that, if it called
gdb_get_line_number, I would have to rip out the call and replace
it with an explicit call to "gdb_test search".
Michael C
prev parent reply other threads:[~2004-08-06 16:06 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-08-05 9:20 Michael Chastain
2004-08-05 13:23 ` Daniel Jacobowitz
2004-08-06 6:26 ` Michael Chastain
2004-08-05 14:34 ` Jim Blandy
2004-08-05 16:02 ` Michael Chastain
2004-08-06 8:24 ` Eli Zaretskii
2004-08-06 9:41 ` Michael Chastain
2004-08-06 14:46 ` Andrew Cagney
2004-08-06 16:06 ` Michael Chastain [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=4113AC7D.nailD201292RT@mindspring.com \
--to=mec.gnu@mindspring.com \
--cc=cagney@gnu.org \
--cc=cagney@redhat.com \
--cc=ezannoni@redhat.com \
--cc=gdb@sources.redhat.com \
--cc=jimb@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