I am willing to bet you are using native threads linked against glibc
2.0.x.
DON'T!
I'm no authority, but one of the developers kindly informed me that
glibc is NOT THREAD SAFE and JDK 1.1.7 doesn't account for this (they
might add code to change this behaviour).
glibc 2.1 IS THREAD SAFE, but breaks things left and right due to
incompats.
SOLUTION:
Use green threads!
I was stress testing an RMI object and saw the same (couldn't believe it
- Java ISN'T supposed to core dump!)...
Green threads made the rmi object solid as a rock.
HTH
Dustin Lang wrote:
>
> Hi,
>
> In fairly normal operation of my fairly large program, I got a "SIGSEGV 11
> segmentation violation". Not the
> right-at-startup-because-you-have-the-wrong-library-version,-stupid type,
> just smack dab in the middle of my code. The same thing happened earlier
> today, but I didn't catch the output. Is there anything I can do with the
> thread dump to figure out what's causing it? Where the crash occurred I
> do a wait-notify, waiting for an RMI network call to dispose a modal
> dialog box.
>
> On a side note, am I correct in assuming that, in threory, there is
> nothing 100% java code can do to cause a virtual machine to crash?
>
> The thread dump is available at http://taz.cs.ubc.ca/java/segfault1.out
>
> I'm not sure if a code snippet will be useful, since that probably won't
> cause a crash.
>
> Oh yeah, this is jdk1.1.7a with kernel 2.2.1.
>
> Thanks very much,
> dstn.
>
> ----------------------------------------------
> Dustin Lang, [EMAIL PROTECTED]
> (java developer,linux guy, all-round goofball)
> ----------------------------------------------
>
> ----------------------------------------------------------------------
> 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]
