Bet? What bet? ;-)
Hmmm...
Green threads solved my problems (I hope this is NOT a case of false
security!)...
Is your version of glibc5 thread safe?
Regardless, this is a very serious issue that I hope the developers can
take a look at.
Now I am REALLY scared. The stuff I work on is as thr
I actually had this happen myself yesterday. I was also running 100%
pure java code. My problem was the result of having some of my class
files out of sync. Since I'm using a makefile, it wasn't necessarily
recompiling all the dependant classes and somehow something got out of
sync with the byteco
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 b
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 outpu
