This is the mail archive of the
java@gcc.gnu.org
mailing list for the Java project.
Re: known synchronized() failures?
- From: Rutger Ovidius <r_ovidius at eml dot cc>
- To: Thomas Aeby <aeby at graeff dot com>
- Cc: java at gcc dot gnu dot org
- Date: Wed, 27 Apr 2005 08:35:39 -0700
- Subject: Re: known synchronized() failures?
- References: <1114597683.6316.23.camel@localhost>
- Reply-to: Rutger Ovidius <r_ovidius at eml dot cc>
Wednesday, April 27, 2005, 3:28:03 AM, you wrote:
TA> The last few days I spent on debuggin a really unpleasant problem. One
TA> of my programs making extensive use of locks ("synchronized") is
TA> reproducibly hanging after a while of operation. After quite some
TA> debugging I'm sure that it is hanging at the start of a synchronized()
TA> block:
I get a 100% cpu use problem, but the gdb bt points to the GC, and
I've been informed that it is due to the use of references overwriting
finalizers (or something to that effect -- I don't fully understand
why it would crash/lock up and can't produce a testcase) (gcc bug
18266).
Maybe you can run it under gdb and look at the bt once it is locked
up.
Regards,
Rutger Ovidius