Date: Fri, 08 Mar 2002 19:32:01 -0700 From: Stacy Millions <stacy@millions.ca> To: "FreeBSD Java mailing list (E-mail)" <freebsd-java@FreeBSD.ORG> Subject: Re: 1.3.1p6 dies sigbus with threads Message-ID: <3C897420.7A4C1061@millions.ca> References: <59063B5B4D98D311BC0D0001FA7E452205FDA3A4@l04.research.kpn.com> <3C7BDF7E.D8645D7@millions.ca>
next in thread | previous in thread | raw e-mail | index | archive | help
Stacy Millions wrote:
> Another data point, I have a simple test program that has the same
> result (as my kids would say, "java goes 'trip, thud'") just by using
> SecureRandom (who fires of a whole load of threads). You have to
> run it about 50 times, but eventually it will dump core. I made
> it a Swing app to get the additional AWT and friends threads to help
> speed up the "trip, thud" process.
I took some time (can you say "was frustrated doing other things" :-)
to try and track this down a bit more. I modified my test program to
fire up a bunch of noise threads (much like what SeedGenerator does)
and it increased the likelihood of a core dump (to about 1 in 5 instead
of 1 in 50). The stack trace is the same in all cases. The annoying part
is, if I run in java_g, I don't get a core dump! I hate bugs like that.
-stacy
--
You'll see it's all a show. Keep 'em laughing as you go.
Just remember that the last laugh is on you.
- Monty Python _The Life Of Brian_
Stacy Millions stacy@millions.ca
Millions Consulting Limited
To Unsubscribe: send mail to majordomo@FreeBSD.org
with "unsubscribe freebsd-java" in the body of the message
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?3C897420.7A4C1061>