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 bytecode. Once I cleaned out all the class files and
recompiled from scratch it was fine.
This may not be your problem, but it is something to watch out for. The
problem happily cause core dumps right in the middle of my test program.
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]
