From: David Carlton <carlton@math.stanford.edu>
To: Elena Zannoni <ezannoni@redhat.com>
Cc: gdb-patches@sources.redhat.com
Subject: Re: [RFA/TESTSUITE] annota1.exp fixes
Date: Thu, 10 Apr 2003 20:34:00 -0000 [thread overview]
Message-ID: <ro1of3edrbu.fsf@jackfruit.Stanford.EDU> (raw)
In-Reply-To: <16021.43826.706488.188589@localhost.redhat.com>
On Thu, 10 Apr 2003 13:34:42 -0400, Elena Zannoni <ezannoni@redhat.com> said:
> Hmm, I've reread the threads and I am none the wiser. We didn't ask the
> emacs people, like Eli suggested.
No. :-(
> I have a revised patch, which works for my problem, but doesn't help
> you. I was wondering if using something like matching on
> (${longversion}|${shortversion}) would work.
It's not the end of the world if my problem never gets solved: I'm
used to seeing those failures, after all. It's a strange situation:
my srcdir is just '.', so ${srcdir}/${subdir}/${srcfile} really is
equivalent to ${subdir}/${srcfile}, GCC is just noticing that it can
leave out the './' at the start when generating debug info. (I'm
pretty sure I checked at the time and made sure that it's GCC that's
getting rid of the './', not GDB.)
So I'm happy enough with your patch; on the other hand, it will cause
Kevin to start seeing failures with the IRIX compiler again, if I'm
reading it right. How about this as a compromise: file a GDB external
suspended PR mentioning that some compilers don't always put full path
names in the debug info, have a pass branch with your new regexp, and
have an xfail branch associated to that PR with your original more
generous regexp? (I'm not sure we do this in the testsuite anywhere
yet, but my understanding is that xfail takes an optional second
argument, which is a PR number.) I think that's a good compromise:
the test should remain useful, because if GDB ever regresses on this
issue then presumably somebody will notice a pass->xfail transition.
And we'll only be saying 'pass' in situations where we're sure we're
doing the right thing.
David Carlton
carlton@math.stanford.edu
next prev parent reply other threads:[~2003-04-10 20:34 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-04-08 22:49 Elena Zannoni
2003-04-09 17:44 ` David Carlton
2003-04-10 17:30 ` Elena Zannoni
2003-04-10 20:34 ` David Carlton [this message]
2003-07-07 15:37 ` Elena Zannoni
2003-07-09 13:21 ` Elena Zannoni
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=ro1of3edrbu.fsf@jackfruit.Stanford.EDU \
--to=carlton@math.stanford.edu \
--cc=ezannoni@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