Illegal Instruction in debug_build

[John Rose]

On Sep 18, 2011, at 1:30 PM, Michael Barker wrote:

> I've been trying to run a debug build on Mac OS, the normal build
> works fine, but the debug version fails with an Illegal Instruction.
> I've run it through gdb (output below), but I not sure how accurate
> the information is.  I think that it's the result of a stack overflow,
> it takes around 2s to fail without any launch class specified.  Has
> anyone witnessed anything similar?

The JVM bootstrap logic does not always robustly report errors.

Try running outside of GDB but with -XX:+ShowMessageBoxOnError.

If you run outside of gdb sometimes you can get extra bits of crash data
from Mac OS or from the JVM's own crash dumper.

I set the "Developer" option in this control panel to get extra backtrace info:
  /Developer/Applications/Utilities/CrashReporterPrefs.app

That will show the OS's idea of the symbolic backtrace.

The JVM should do this also in its crash dump logs, but doesn't on Mac OS.

I have recently had a bug in the JVM's bootstrap logic (in tagu.patch),
which reported awkwardly by blowing the stack in the error reporter.
That may be happening for you also.  The Mac OS popup was helpful
to diagnose this.

Good luck!

-- John
-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://mail.openjdk.java.net/pipermail/mlvm-dev/attachments/20110930/27bdbf10/attachment.html