From: Kevin Buettner <kevinb@redhat.com>
To: Fernando Nasser <fnasser@redhat.com>
Cc: gdb-patches@sources.redhat.com
Subject: Re: [PATCH RFA] New constvars.exp tests
Date: Thu, 17 Oct 2002 17:11:00 -0000 [thread overview]
Message-ID: <1021018001122.ZM14289@localhost.localdomain> (raw)
In-Reply-To: Kevin Buettner <kevinb@redhat.com> "Re: [PATCH RFA] New constvars.exp tests" (Oct 17, 1:31pm)
On Oct 17, 1:31pm, Kevin Buettner wrote:
> On Oct 17, 4:06pm, Fernando Nasser wrote:
>
> > This looks good. If I am not mistaken, your patch that fixes the
> > printing has been already committed so these tests will either PASS or
> > XFAIL.
>
> You're right; the patch is in, but I recall seeing XPASSes for my new
> tests (along with a lot of other tests) when I used Dwarf 2. I
> suspect that something's going wrong with the following code:
>
> proc local_compiler_xfail_check { } {
> global gcc_compiled;
>
> if {$gcc_compiled} then {
> if { ![test_debug_format "HP"] \
> && ![test_debug_format "DWARF 2"] } then {
> setup_xfail "*-*-*"
> }
> }
> }
>
> I'm double checking and looking into it now...
It turns out that the above check is okay. It's gdb's ``info source''
command which is having problems. When I configure & build gdb using
absolute paths, I'm NOT seeing the problem, but when I'm using relative
paths, I am. Still haven't completely figured it out yet.
Anyway, I don't think it's a testsuite problem, but a gdb problem
instead.
Kevin
next prev parent reply other threads:[~2002-10-18 0:11 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-10-10 13:33 Kevin Buettner
2002-10-10 13:39 ` Daniel Jacobowitz
2002-10-17 13:08 ` Fernando Nasser
2002-10-17 13:31 ` Kevin Buettner
2002-10-17 17:11 ` Kevin Buettner [this message]
2002-10-17 13:25 ` Kevin Buettner
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=1021018001122.ZM14289@localhost.localdomain \
--to=kevinb@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