From: Mark Kettenis <mark.kettenis@xs4all.nl>
To: vladimir@codesourcery.com
Cc: gdb-patches@sources.redhat.com
Subject: Re: Extra diagnostic for tests
Date: Wed, 13 Sep 2006 10:20:00 -0000 [thread overview]
Message-ID: <200609131018.k8DAI1rt026498@elgar.sibelius.xs4all.nl> (raw)
In-Reply-To: <200609131352.16082.vladimir@codesourcery.com> (message from Vladimir Prus on Wed, 13 Sep 2006 13:52:16 +0400)
> From: Vladimir Prus <vladimir@codesourcery.com>
> Date: Wed, 13 Sep 2006 13:52:16 +0400
>
> Hi,
> at the moment, the dejagnu tests use PATH to find the gdb binary, and don't
> report which gdb binary is used. As result, when running runtest manually on
> one test, one can test with different gdb from the one used by 'make check'.
There must be something wrong with your setup. I have a gdb somewhere
in my PATH, but I'm damn sure the testsuite picks up the gdb in my
build tree.
Mark
next prev parent reply other threads:[~2006-09-13 10:20 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-09-13 9:52 Vladimir Prus
2006-09-13 10:20 ` Mark Kettenis [this message]
2006-09-13 12:24 ` Daniel Jacobowitz
2006-09-13 17:58 ` Michael Snyder
2006-09-16 11:19 ` Vladimir Prus
2006-09-16 14:20 ` Daniel Jacobowitz
2006-09-23 16:55 ` Mark Kettenis
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=200609131018.k8DAI1rt026498@elgar.sibelius.xs4all.nl \
--to=mark.kettenis@xs4all.nl \
--cc=gdb-patches@sources.redhat.com \
--cc=vladimir@codesourcery.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