This is the mail archive of the
java-patches@gcc.gnu.org
mailing list for the Java project.
RE: dl_iterate_phdr() deadlock patch
- From: Andrew Haley <aph at redhat dot com>
- To: "Boehm, Hans" <hans_boehm at hp dot com>
- Cc: "'tromey at redhat dot com'" <tromey at redhat dot com>,"'java-patches at gcc dot gnu dot org'" <java-patches at gcc dot gnu dot org>
- Date: Mon, 10 Mar 2003 20:22:47 +0000 (GMT)
- Subject: RE: dl_iterate_phdr() deadlock patch
- References: <75A9FEBA25015040A761C1F74975667D01441F45@hplex4.hpl.hp.com>
Boehm, Hans writes:
> I checked in the patch a while ago (Mar. 4). If you're still
> seeing problems, that's news to me. Please post details. Is this
> still a deadlock? For a dynamically linked executable? Can you
> send gdb stack traces?
It could be that the test just runs for a log time rather than
actually failing. I'll investigate further.
Andrew.
> > -----Original Message-----
> > From: Andrew Haley [mailto:aph at redhat dot com]
> > Sent: Monday, March 10, 2003 11:25 AM
> > To: Boehm, Hans
> > Cc: 'tromey at redhat dot com'; 'java-patches at gcc dot gnu dot org'
> > Subject: RE: dl_iterate_phdr() deadlock patch
> >
> >
> > Boehm, Hans writes:
> > > A quick status update:
> > >
> > > I checked the patch into the trunk.
> > >
> > > I then decided to run SPECjbb on X86 as one last test before
> > > checking it into 3.3. That failed. It turns out that
> > > dl_iterate_phdr() apparently doesn't issue a callback for the main
> > > executable in a completely statically linked program, though it
> > > appears to do so if the program is linked against any dynamic
> > > libraries.
> > >
> > > I am generating a small patch to work around this. Unless I hear
> > > otherwise, I will check the result into 3.3 very soon, and update
> > > the trunk correspondingly.
> >
> > No luck yet? I'm still getting failures on 3.3 branch.
> >
> > Andrew.
> >