I've seen similar beharvior on a RedHat 7.1 system with
a 2.4.2 kernel:
[user@system]$ java -version
java version "1.3.1"
Java(TM) 2 Runtime Environment, Standard Edition (build Blackdown-1.3.1-FCS)
Java HotSpot(TM) Client VM (build Blackdown-1.3.1-FCS, mixed mode)
****************
Another exception has been detected while we were handling last error.
Dumping information about last error:
ERROR REPORT FILE = (N/A)
PC = 0x0x4026b988
SIGNAL = 11
FUNCTION NAME = (N/A)
LIBRARY NAME = (N/A)
Please check ERROR REPORT FILE for further information, if there is any.
Good bye.
Aborted
"Michael ." wrote:
>
> 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
> >
--
wYRd.:|:[EMAIL PROTECTED]:|:.prohibitions void where offered
de recta non tolerandum sunt
----------------------------------------------------------------------
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
