From: David Carlton <carlton@math.stanford.edu>
To: Fernando Nasser <fnasser@redhat.com>
Cc: Elena Zannoni <ezannoni@redhat.com>, gdb-patches@sources.redhat.com
Subject: Re: [PATCH] Make tests more flexible
Date: Thu, 16 Jan 2003 17:10:00 -0000 [thread overview]
Message-ID: <ro1k7h558dc.fsf@jackfruit.Stanford.EDU> (raw)
In-Reply-To: <3E26C44E.2050500@redhat.com>
On Thu, 16 Jan 2003 09:40:14 -0500, Fernando Nasser <fnasser@redhat.com> said:
> I see a few other files with the
> set srcfile ${srcdir}/${subdir}/${testfile}.c
> line. They should be breaking runs with "different test tree
> configurations" as well.
> display.exp:set srcfile ${srcdir}/${subdir}/${testfile}.c
> long_long.exp:set srcfile ${srcdir}/${subdir}/${testfile}.c
> mips_pro.exp:set srcfile ${srcdir}/$subdir/${testfile}.c
> overlays.exp:set srcfile ${srcdir}/${subdir}/${testfile}.c
> relocate.exp:set srcfile ${srcdir}/${subdir}/${testfile}.c
> setshow.exp:set srcfile ${srcdir}/${subdir}/${testfile}.c
> step-line.exp:set srcfile ${srcdir}/${subdir}/${testfile}.c
> step-test.exp:set srcfile ${srcdir}/${subdir}/${testfile}.c
For what it's worth, all those files pass for me. But that doesn't
mean much; they might not use srcfile in ways that trigger this
particular bug, and one of them (overlays.exp) doesn't actually do
anything on my platform. So we might as well convert them all to use
the proper definition of srcfile, it seems to me.
David Carlton
carlton@math.stanford.edu
next prev parent reply other threads:[~2003-01-16 17:10 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-01-16 2:05 Elena Zannoni
2003-01-16 4:50 ` David Carlton
2003-01-16 17:19 ` Elena Zannoni
2003-01-16 14:40 ` Fernando Nasser
2003-01-16 16:40 ` Elena Zannoni
2003-01-16 17:10 ` David Carlton [this message]
2003-01-16 17:27 ` Elena Zannoni
2003-01-16 4:36 Michael Elizabeth Chastain
2003-01-16 17:24 Michael Elizabeth Chastain
2003-01-16 17:27 Michael Elizabeth Chastain
2003-01-16 17:35 Michael Elizabeth Chastain
2003-01-16 17:53 ` Elena Zannoni
2003-01-16 18:07 Michael Elizabeth Chastain
2003-01-16 18:45 Michael Elizabeth Chastain
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=ro1k7h558dc.fsf@jackfruit.Stanford.EDU \
--to=carlton@math.stanford.edu \
--cc=ezannoni@redhat.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