From: Andrew Cagney <cagney@gnu.org>
To: Manoj Iyer <manjo@austin.ibm.com>
Cc: gdb@sources.redhat.com
Subject: Re: testsuite questions.
Date: Sat, 24 Apr 2004 00:03:00 -0000 [thread overview]
Message-ID: <40896B3C.2010203@gnu.org> (raw)
In-Reply-To: <Pine.LNX.4.58.0404231238580.1561@lazy>
> I am trying to compare the test results from the GDB I built vs the GDB
> installed on the system. I found that if I set GDB "/usr/bin/mygdb" in the
> testcases.exp file, the testcase uses my custom GDB instead of searching
> for one in src/gdb/.
>
> 1. Is there any enviroment variable that I can set to make the testcase
> use my custom GDB, for instance the one in /usr/local/bin/gdb?
I don't remember.
> Also, when the testcase '.c' file is compiled, the compile line ignores
> any CFLAGS or CC variables that I set, I found that gdb_compile and
> target-compile use CFLAGS_FOR_TARGET and CC_FOR_TARGET varialbles. I would
> like to use my custom compiler and compile the testcase as a 64bit binary
> (-m64 flag).
You need to pass the stuff to dejagnu. For this, I'd recommend:
make check 'RUNTESTFLAFS=--target_board=unix/-m32\ unix/-m64'
however, 'RUNTESTFLAGS=... CFLAGS_FOR_TARGET=...' also has an effect.
> 2. Is there any enviroment variable I can use to control the value of
> these variables?
>
> The intention is to disconnect the testsuite from using the system
> utilities and GDB that gets built, but use the testcase to test a
> different binary of GDB that I have in a separate local/system directory.
> This way I can compare the test results from system gdb (or any gdb binary
> forthat matter) with the one that I downloaded from cvs.
>
> Any input is greatly appreciated.
>
> Thanks
> Manjo
next prev parent reply other threads:[~2004-04-24 0:03 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-04-23 18:15 Manoj Iyer
2004-04-24 0:03 ` Andrew Cagney [this message]
2004-04-24 0:03 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=40896B3C.2010203@gnu.org \
--to=cagney@gnu.org \
--cc=gdb@sources.redhat.com \
--cc=manjo@austin.ibm.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