This error, incidentally, comes about half the time,
running the command line repeatedly. Adding "-Xrs"
reduces the occurrence to about 1 out of 10 times (and
gives a different PC value, no surprise). Running from
jdb, the error doesn't occur at all.
Leads me to suspect a bug in java's shutdown code.
If anyone else has seen this behavior (or not), I'd
like to know your configuration.
> $ java greetings.Hello World Universe Everyone
> [...]
> Another exception has been detected while we were
> handling last error.
> Dumping information about last error:
> ERROR REPORT FILE = (N/A)
> PC = 0x0x4025e988
> SIGNAL = 11
> FUNCTION NAME = (N/A)
> LIBRARY NAME = (N/A)
> Please check ERROR REPORT FILE for further
> information, if there is any.
> Good bye.
> Segmentation fault
>
------------------------------------------------------
>
> Sometimes the error message doesn't appear (i.e.,
> all
> looks as expected).
__________________________________________________
Do You Yahoo!?
Make international calls for as low as $.04/minute with Yahoo! Messenger
http://phonecard.yahoo.com/
----------------------------------------------------------------------
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
