[Gc] [w3m-dev-en 00993] Re: Solaris 8 build of 0.4.2 (fwd)
hans.boehm at hp.com
Mon Mar 29 13:16:00 PST 2004
The first thing to do is to verify that "./configure; make; make check"
or "make test" in the gc directory works correctly.
If that doesn't report any errors, we'd really need a stack trace of the hung
process obtained, e.g. by running it in a debugger for a while, and then
interrupting it. Or it might be easier to get it to generate a core dump
and then get a debugger to extract a stack trace from that.
> -----Original Message-----
> From: gc-bounces at napali.hpl.hp.com
> [mailto:gc-bounces at napali.hpl.hp.com]On Behalf Of Steven F. Killen
> Sent: Monday, March 29, 2004 11:44 AM
> To: gc at napali.hpl.hp.com
> Subject: [Gc] [w3m-dev-en 00993] Re: Solaris 8 build of 0.4.2 (fwd)
> Attached is a problem I'm experiencing in trying to build w3m
> 0.4.2 with
> gc 6.3alpha2. I'm using gcc 3.2.1. Is there any information
> I could give
> that would clarify the matter further?
> Steve Killen <skille1 at umbc.edu>
> ---------- Forwarded message ----------
> Date: Thu, 25 Mar 2004 03:12:36 +0900
> From: Fumitoshi UKAI <ukai at debian.or.jp>
> Reply-To: w3m-dev-en at mi.med.tohoku.ac.jp
> To: w3m-dev-en at mi.med.tohoku.ac.jp
> Cc: Steven F. Killen <skille1 at umbc.edu>
> Subject: [w3m-dev-en 00993] Re: Solaris 8 build of 0.4.2
> At Mon, 22 Mar 2004 15:33:38 -0500 (EST),
> Steven F. Killen wrote:
> > I'm trying to build w3m 0.4.2 on Solaris 8, with gc
> 6.3alpha2. It builds
> > fine on Irix 6.5 and Linux 2.4, but on Solaris it gets caught up on
> > mktable.
> > Apparently mktable goes to sleep. When it reaches
> > ./mktable 100 functable.tab > functable.c
> > in the build, it simply hangs there.
> > The process shows as
> > 8 S skille1 20921 20834 0 51 20 ? 322
> ? 15:22:13
> > pts/5 0:00 ./mktable 100 functable.tab
> > and functable.c is filesize 0, which leads me to believe mktable is
> > getting caught up somewhere.
> > Is there any other information that would help with this?
> In most case, this case of build failure comes from a problem
> of your libgc.
> Fumitoshi UKAI
> Gc mailing list
> Gc at linux.hpl.hp.com
More information about the Gc