Mirror of the gdb-patches mailing list
 help / color / mirror / Atom feed
From: Daniel Jacobowitz <drow@false.org>
To: gdb-patches@sourceware.org
Subject: Re: [RFA] Allow use of breakpoint commands inside `if' or `while'
Date: Sat, 14 Jan 2006 16:28:00 -0000	[thread overview]
Message-ID: <20060114162746.GA13170@nevyn.them.org> (raw)
In-Reply-To: <u7j9222yd.fsf@gnu.org>

On Sat, Jan 14, 2006 at 06:23:38PM +0200, Eli Zaretskii wrote:
> > Date: Sat, 14 Jan 2006 10:49:09 -0500
> > From: Daniel Jacobowitz <drow@false.org>
> > 
> > On Fri, Jan 13, 2006 at 06:02:35PM +0200, Eli Zaretskii wrote:
> > > You mean in gdb.base/commands.exp?  I suppose I could do that, but I
> > > don't have a test suite set up anywhere on the machines to which I
> > > have access, so it might not be easy for me to test the tests I add.
> > 
> > That's very unfortunate - it's standard practice to insist that code
> > patches be tested by the testsuite.
> 
> Yes, I know.  Any pointers to howto set up a test suite from scratch
> with minimal pain (on a Debian box)?  I might give it a try on some
> rainy day.

Sure - it's trivial.  Just install the package "dejagnu" using apt,
and then run the testsuite using "make check-gdb" from the top level or
"make check" from the GDB subdirectory.

You will definitely get a handful of failures (which I'm not thrilled
about, but no longer have the energy to fight against).  So run it once
before changing anything and hold on to those baselines.  There's also
a small set of random failures, related to timing - interrupt tests and
thread tests.

-- 
Daniel Jacobowitz
CodeSourcery


  reply	other threads:[~2006-01-14 16:28 UTC|newest]

Thread overview: 15+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-01-13 14:48 Eli Zaretskii
2006-01-13 15:32 ` Daniel Jacobowitz
2006-01-13 16:02   ` Eli Zaretskii
2006-01-14 15:49     ` Daniel Jacobowitz
2006-01-14 16:23       ` Eli Zaretskii
2006-01-14 16:28         ` Daniel Jacobowitz [this message]
2006-01-15  4:29           ` Eli Zaretskii
2006-01-15 10:42             ` Andreas Schwab
2007-01-13 17:11 ` Eli Zaretskii
2007-01-13 17:21   ` Eli Zaretskii
2007-01-20 20:34     ` Daniel Jacobowitz
2007-01-27 12:24       ` Eli Zaretskii
2007-01-29 16:21         ` Daniel Jacobowitz
2007-01-20 20:04   ` Daniel Jacobowitz
2007-01-27 12:31     ` 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=20060114162746.GA13170@nevyn.them.org \
    --to=drow@false.org \
    --cc=gdb-patches@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