From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 21568 invoked by alias); 2 Apr 2002 03:49:32 -0000 Mailing-List: contact gdb-patches-help@sources.redhat.com; run by ezmlm Precedence: bulk List-Subscribe: List-Archive: List-Post: List-Help: , Sender: gdb-patches-owner@sources.redhat.com Received: (qmail 21452 invoked from network); 2 Apr 2002 03:49:30 -0000 Received: from unknown (HELO nevyn.them.org) (128.2.145.6) by sources.redhat.com with SMTP; 2 Apr 2002 03:49:30 -0000 Received: from drow by nevyn.them.org with local (Exim 3.35 #1 (Debian)) id 16sFIX-0007Mf-00; Mon, 01 Apr 2002 22:49:29 -0500 Date: Mon, 01 Apr 2002 19:49:00 -0000 From: Daniel Jacobowitz To: Michael Elizabeth Chastain Cc: fnasser@redhat.com, gdb-patches@sources.redhat.com Subject: Re: [RFA/testsuite] Tweak gdb.java/jmisc.java to pass on PowerPC Message-ID: <20020401224929.A28287@nevyn.them.org> Mail-Followup-To: Michael Elizabeth Chastain , fnasser@redhat.com, gdb-patches@sources.redhat.com References: <200204020342.g323gxc09149@duracef.shout.net> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <200204020342.g323gxc09149@duracef.shout.net> User-Agent: Mutt/1.3.23i X-SW-Source: 2002-04/txt/msg00011.txt.bz2 On Mon, Apr 01, 2002 at 09:42:59PM -0600, Michael Elizabeth Chastain wrote: > Daniel Jacobowitz writes: > > [this is especially nasty because failing to print a Java array makes GDB > > very sad. It loops for hours, walking up the stack (very slowly because of > > thread_db). We then kill gdb, which may or may not kill jmisc, so the > > testsuite tends to leave zombies lying around.] > > Maybe my view of the world is a little twisted, but I think a test case > is good when it makes gdb lose its mind. I am in favor of changing the > test suite to work around bugs in compilers and other tools that are > outside our responsibility but gdb is inside our responsibility. > > > This patch adds a use of the argument after the prologue, so that it will > > still be available to print. OK to commit? > > I would rather keep the original test and file a bug report. Perhaps > clone the test so that you can test the behavior that you want to test > as well as banging on the broken behavior. That's a good view of the world. It's not practical in this case unless you're volunteering to fix it, though :) This bug causes a testsuite run via | tee to hang forever. Testsuites are no good if we can't run them! Bug reports are good for tracking, but I would prefer filing a bug on the fact that Java will print unreasonably long arrays (i.e. corrupt length field). -- Daniel Jacobowitz Carnegie Mellon University MontaVista Software Debian GNU/Linux Developer