From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 1482 invoked by alias); 27 Jun 2006 16:05:16 -0000 Received: (qmail 1139 invoked by uid 22791); 27 Jun 2006 16:05:14 -0000 X-Spam-Check-By: sourceware.org Received: from mx1.redhat.com (HELO mx1.redhat.com) (66.187.233.31) by sourceware.org (qpsmtpd/0.31) with ESMTP; Tue, 27 Jun 2006 16:05:11 +0000 Received: from int-mx1.corp.redhat.com (int-mx1.corp.redhat.com [172.16.52.254]) by mx1.redhat.com (8.12.11.20060308/8.12.11) with ESMTP id k5RG5A5i019306; Tue, 27 Jun 2006 12:05:10 -0400 Received: from pobox.toronto.redhat.com (pobox.toronto.redhat.com [172.16.14.4]) by int-mx1.corp.redhat.com (8.12.11.20060308/8.12.11) with ESMTP id k5RG59qH020644; Tue, 27 Jun 2006 12:05:09 -0400 Received: from [172.16.14.92] (tortoise.toronto.redhat.com [172.16.14.92]) by pobox.toronto.redhat.com (8.12.8/8.12.8) with ESMTP id k5RG58ve001787; Tue, 27 Jun 2006 12:05:09 -0400 Message-ID: <44A15734.8030708@redhat.com> Date: Tue, 27 Jun 2006 16:05:00 -0000 From: Thomas Fitzsimmons User-Agent: Thunderbird 1.5.0.2 (X11/20060501) MIME-Version: 1.0 To: Mark Wielaard CC: Anthony Balkissoon , mauve-patches@sources.redhat.com Subject: Re: RFC: add "not-a-test" tag to several tests References: <1151080291.25174.104.camel@tony.toronto.redhat.com> <1151331641.3361.8.camel@localhost.localdomain> <1151332775.2701.16.camel@elsschot.wildebeest.org> <44A00DF9.9040306@redhat.com> <1151340576.2557.3.camel@elsschot.wildebeest.org> In-Reply-To: <1151340576.2557.3.camel@elsschot.wildebeest.org> Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit X-IsSubscribed: yes Mailing-List: contact mauve-patches-help@sourceware.org; run by ezmlm Precedence: bulk List-Subscribe: List-Archive: List-Post: List-Help: , Sender: mauve-patches-owner@sourceware.org X-SW-Source: 2006/txt/msg00485.txt.bz2 Mark Wielaard wrote: > On Mon, 2006-06-26 at 12:40 -0400, Thomas Fitzsimmons wrote: >> Mark Wielaard wrote: >>> They make it possible to use >>> RunnerProcess just as you could use SimpleTestHarness (e.g. echo >>> gnu.testlet.some.test | runtime RunnerProcess) by just returning when >>> stdin is empty (and in.readLine() returns null). >> This can already be done using the current Harness: >> >> jamvm Harness gnu.testlet.some.test >> >> Harness also supports specifying multiple tests: >> >> jamvm Harness gnu/testlet/java/awt/Frame/size1.java >> gnu/testlet/javax/swing/JTable/addColumn.java > > I know, but that is a terrible way for debugging. Hunting down a crasher > bug for example is really, really awkward using the Harness since it > does way too many things. When examining tests (especially under gdb) > for debugging you need to be able to run them just through the > RunnerProcess to make sure you are looking at just the thing that fails. > It works nicely with that one-liner patch though, so it isn't really > another way to run tests, it is just to make sure you can run the tests > by hand as if the Harness would run them. Why don't we just print the VM command-line invocation as part of Harness's output? Then you could simply copy-n-paste that to gdb --args. Tom