From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 9356 invoked by alias); 14 Jan 2006 16:28:21 -0000 Received: (qmail 9347 invoked by uid 22791); 14 Jan 2006 16:28:21 -0000 X-Spam-Check-By: sourceware.org Received: from nevyn.them.org (HELO nevyn.them.org) (66.93.172.17) by sourceware.org (qpsmtpd/0.31.1) with ESMTP; Sat, 14 Jan 2006 16:27:48 +0000 Received: from drow by nevyn.them.org with local (Exim 4.54) id 1ExoFm-0003Rh-5N for gdb-patches@sourceware.org; Sat, 14 Jan 2006 11:27:46 -0500 Date: Sat, 14 Jan 2006 16:28:00 -0000 From: Daniel Jacobowitz To: gdb-patches@sourceware.org Subject: Re: [RFA] Allow use of breakpoint commands inside `if' or `while' Message-ID: <20060114162746.GA13170@nevyn.them.org> Mail-Followup-To: gdb-patches@sourceware.org References: <20060113153213.GA10138@nevyn.them.org> <20060114154909.GB12028@nevyn.them.org> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: User-Agent: Mutt/1.5.8i X-IsSubscribed: yes Mailing-List: contact gdb-patches-help@sourceware.org; run by ezmlm Precedence: bulk List-Subscribe: List-Archive: List-Post: List-Help: , Sender: gdb-patches-owner@sourceware.org X-SW-Source: 2006-01/txt/msg00159.txt.bz2 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 > > > > 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