SV: GCJ 3.3 crash with string handling reproduceable case
Øyvind Harboe
oyvind.harboe@zylin.com
Thu Feb 27 10:33:00 GMT 2003
>I've just deployed a minGW application compiled by 3.3.
>>Does the problem with garbage collection mean that memory won't be
>recovered, and that the application will starve? I mean, is this something
>that will bring down the application and even the entire OS?
>>Should I recall the application, and compile with 3.2 instead?
Since my app dies under 3.3, even though garbage collection "works". I have no choice but to
deploy with 3.2. If you're using multithreading, I think you are especially vulnerable, though I
couldn't say if you are safe w/single threading. I've had very good feedback on my app
compiled w/MinGW 3.2.
Perhaps I'm harder hit by this problem than the rest of the world, but I don't think anybody would
argue the importance of fixing this problem.
Øyvind
Like off-piste? http://www.harboe.org/oyvind/davos/davos.html
More information about the Java
mailing list