From: Daniel Jacobowitz <drow@false.org>
To: Aman Wardak <aman.wardak@gmail.com>
Cc: gdb@sourceware.org
Subject: Re: many tests restart gdbserver
Date: Tue, 13 Feb 2007 15:43:00 -0000 [thread overview]
Message-ID: <20070213115934.GA9148@caradoc.them.org> (raw)
In-Reply-To: <cea22a0c0702121933o1365beb7v5bfad7c0d1bb7db8@mail.gmail.com>
On Mon, Feb 12, 2007 at 07:33:11PM -0800, Aman Wardak wrote:
> When the testsuite is run in a cross environment, many of the tests
> start up the gdbserver on the target twice and only use the second
> instance.
>
> lib/gdb.exp:gdb_start() starts the first instance
> lib/gdb.exp:runto_main() starts the second
>
> Is this actually done for a purpose (maybe its needed to do this
> sometimes) ? Or can we optimize this? Has anyone looked at it?
I never figured out a way to get the testsuite to work without this.
If you can, be my guest! I plan to try again sometime, but it won't
be any time soon.
--
Daniel Jacobowitz
CodeSourcery
prev parent reply other threads:[~2007-02-13 11:59 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-02-13 15:29 Aman Wardak
2007-02-13 15:43 ` Daniel Jacobowitz [this message]
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=20070213115934.GA9148@caradoc.them.org \
--to=drow@false.org \
--cc=aman.wardak@gmail.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