This is the mail archive of the
java@gcc.gnu.org
mailing list for the Java project.
Re: known synchronized() failures?
Bryce McKinlay wrote:
There is a known bug in the synchronization implementation prior to
GCC 4.0 - see PR 16662. Unfortunately that fix doesn't seem to have
made it into the 3.4 branch.
However, the symptoms of that problem are an
IllegalMonitorStateException - I'm not aware of any bugs that would
cause the symptoms you describe.
Interesting thread, as I use 3.4.3 and would want to make it "better".
So, actually I should grab the natObject.cc from CVS (or 1.31 at
least), and then sync'ing should be at least as good as before.
That should work, I think. I can't recall any other changes to natObject
that would make it incompatible, but its possible you may have to hack
it slightly.
Oki...
I haven't seen any IllegalMonitorStateException yet, though, but I
surely don't wanna have them comming when my application is out and
running in the field.
Yes, although note that we only ever saw 16662 on MP systems - it
shouldn't be a problem on a uniprocessor machine.
Ohhhh - I missed the "dual" part in the bug-statement:
"I can also reproduce the problem on a dual PII/266 machine, though it
seems to often take a while."
Silly me...
Thanks,
Martin