This is the mail archive of the
java@gcc.gnu.org
mailing list for the Java project.
Re: libjava testsuite failures (regressions 3.2 -> 3.3)
- From: Andrew Haley <aph at redhat dot com>
- To: Jeff Sturm <jsturm at one-point dot com>
- Cc: Mark Wielaard <mark at klomp dot org>,"Boehm, Hans" <hans_boehm at hp dot com>, Tom Tromey <tromey at redhat dot com>,Matthias Klose <doko at cs dot tu-berlin dot de>, <java at gcc dot gnu dot org>
- Date: Sat, 18 Jan 2003 17:02:22 +0000 (GMT)
- Subject: Re: libjava testsuite failures (regressions 3.2 -> 3.3)
- References: <1042889501.24526.236.camel@elsschot><Pine.LNX.4.44.0301180928180.22948-100000@ops2.one-point.com>
Jeff Sturm writes:
> On 18 Jan 2003, Mark Wielaard wrote:
> > We could do the same kind of thing, but this does not seem to be the
> > root cause of this problem. The SyncTest as compiled by gcj -C seems to
> > have a real deadlock some of the times (this does never happen with gij
> > 3.2 it seems, which is also much faster on this test then gij 3.3).
Good catch!
> I see... Class.forName() now calls _Unwind_FindEnclosingFunction which
> needs dl_iterate_phdr. (That also explains why 3.3 is much slower on this
> test.) Thanks for the stack dump. I hadn't gotten a deadlock yet, but I
> may have just been lucky.
>
> I guess the simplest workaround is to #undef HAVE_DL_ITERATE_PHDR?
I think so. This has been a latent bug for a long time -- other
places in libgcc also call dl_iterate_phdr().
Andrew.