From: Daniel Jacobowitz <drow@false.org>
To: gdb-patches@sources.redhat.com
Subject: Re: RFC: Gdbserver unit testing
Date: Fri, 08 Apr 2005 12:58:00 -0000 [thread overview]
Message-ID: <20050408125741.GB32446@nevyn.them.org> (raw)
In-Reply-To: <20050327030054.GA10766@nevyn.them.org>
On Sat, Mar 26, 2005 at 10:00:54PM -0500, Daniel Jacobowitz wrote:
> Something Andrew suggested to me a long time ago. This patch refactors the
> gdbserver testsuite support routines so that they can be used concurrently
> with a native test. If gdbserver has been built, it will be tested. If it
> hasn't, the tests will be quietly skipped. How's it look? The only test
> using the machinery is trivial; it verifies that gdbserver starts, and that
> we can connect to it, and run to a breakpoint.
>
> Eli, this creates gdb.gdbserver/ next to gdb.gdb/; what does this mean for
> fnchange.lst? Do I need to find a different name for the directory?
It means everything in it gets fnchange.lst entries; there is an
example for gdb.gdbtk already.
> 2005-03-26 Daniel Jacobowitz <dan@codesourcery.com>
>
> * Makefile.in (ALL_SUBDIRS): Add gdb.gdbserver.
> * configure.ac: Create gdb.gdbserver/Makefile.
> * lib/gdbserver-support.exp: New file, derived from
> config/gdbserver.exp.
> * config/gdbserver.exp: Use gdbserver-support.exp.
> * gdb.gdbserver/Makefile.in: New file.
> * gdb.gdbserver/server.c: New file.
> * gdb.gdbserver/server-run.exp: New file.
Checked in now. Please let me know if it misbehaves.
--
Daniel Jacobowitz
CodeSourcery, LLC
next prev parent reply other threads:[~2005-04-08 12:58 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-03-27 3:00 Daniel Jacobowitz
2005-04-08 12:58 ` Daniel Jacobowitz [this message]
2005-04-09 8:14 ` Eli Zaretskii
2005-04-11 14:13 ` Daniel Jacobowitz
2005-04-11 20:18 ` Eli Zaretskii
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=20050408125741.GB32446@nevyn.them.org \
--to=drow@false.org \
--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