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

[Michael Elizabeth Chastain <mec at shout dot net>]

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.

My two cents,

Michael C