If this is a JNI program you may get more verification that it was inside
your own code or from the VM from running with -classic .
The new 1.3.1 release will have better hotspot diagnostics than the cryptic
message below. If you do 'man ascii' you can read off the file name below,
(its in hex) the last 4 digits are the line number. ie os_linux.cpp 1468
There have been some bugs in relation to null arguments with JNI which
I would guess can be coded around for now
regards
calvin
Joi Ellis wrote:
>
> On 9 Apr 2001, Zhihong Pan wrote:
>
> > When I call c function in my java application, I got the following error message:
> > #
> > # HotSpot Virtual Machine Error, Unexpected Signal 11
> > # Please report this error at
> > # http://java.sun.com/cgi-bin/bugreport.cgi
> > #
> > # Error ID: 4F533F4C494E55580E43505005BC
> > #
> > # Problematic Thread: prio=1 tid=0x804e500 nid=0x7062 runnable
> > #
> > 18Aborted
>
> Stick that long number into Bug Parade's search engin.
> I remember looking for it a few weeks ago. Either I found
> a workaround or took a different road around it, I don't remember
> which.
>
> --
> Joi Ellis Software Engineer
> Aravox Technologies [EMAIL PROTECTED], [EMAIL PROTECTED]
>
> No matter what we think of Linux versus FreeBSD, etc., the one thing I
> really like about Linux is that it has Microsoft worried. Anything
> that kicks a monopoly in the pants has got to be good for something.
> - Chris Johnson
>
> ----------------------------------------------------------------------
> To UNSUBSCRIBE, email to [EMAIL PROTECTED]
> with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
----------------------------------------------------------------------
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
