From: "Doug Evans" <dje@google.com>
To: gdb@sourceware.org
Subject: Running testsuite on linux with gdbserver.
Date: Wed, 16 Jan 2008 23:30:00 -0000 [thread overview]
Message-ID: <e394668d0801161529v752502ecpfba99a911e53f575@mail.gmail.com> (raw)
If I hack dejagnu/framework.exp:is_remote to treat linux-gdbserver as
a non-remote target, the following works:
bash$ runtest --tool gdb --target_board linux-gdbserver
target = i686-linux
Here is the hack:
proc is_remote { board } {
[...]
+ if { $board == "linux-gdbserver" } {
+ verbose "board is $board, not remote" 3
+ return 0;
+ }
# We're on the "build". The check for the empty string is just for
# paranoia's sake--we shouldn't ever get one. "unix" is a magic
# string that should really go away someday.
if { $board == "build" || $board == "unix" || $board == "" } {
verbose "board is $board, not remote" 3
return 0
}
Note that dejagnu thinks unix is remote [board_info(unix,isremote) ==
1] but it still works because of the above hack to watch for $board ==
"unix".
Do folks ever test gdbserver this way? Am I doing something wrong
that makes the above hack necessary?
next reply other threads:[~2008-01-16 23:30 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-01-16 23:30 Doug Evans [this message]
2008-01-17 14:39 ` Daniel Jacobowitz
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=e394668d0801161529v752502ecpfba99a911e53f575@mail.gmail.com \
--to=dje@google.com \
--cc=gdb@sourceware.org \
/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;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).