Re: [RFA/testsuite] Tweak gdb.java/jmisc.java to pass on PowerPC

[Daniel Jacobowitz <drow@mvista.com>]

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 <file> 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