Thu, 2 Oct 2003 20:09:07 -0600
Amazing coincidence! I was just reading about this when this message
arrived. A good page giving details is
> -----Original Message-----
> From: firstname.lastname@example.org [mailto:email@example.com] On
> Behalf Of Boehm, Hans
> Sent: Thursday, October 02, 2003 5:59 PM
> To: 'Giuseppe Attardi'; firstname.lastname@example.org
> Subject: RE: [Gc] SIGPWR
> You should ignore those, and tell your debugger to simply pass them
> and let the program handle them.
> In its default configuration under Linux, with threads enabled, the
> sends and catches those signals to stop and restart threads during a
> However, you are likely to have problems with the combination of redirect-
> and threads. Dealing with that is on my list. The problem is that with
> the collecting allocator tends to get invoked during startup of the
> pthreads system.
> But it calls into pthreads for locks, etc. If you can do the malloc
> redirection with
> macros instead (so that the system startup code sees the system malloc),
> things would
> be far easier.
> > -----Original Message-----
> > From: Giuseppe Attardi [mailto:email@example.com]
> > Sent: Thursday, October 02, 2003 3:09 PM
> > To: firstname.lastname@example.org
> > Subject: [Gc] SIGPWR
> > I am trying to use the gc as a leak detector for a multithreaded
> > application,
> > on Linux RH 7.3 with gcc 2.96.
> > I have configured it with
> > configure --enable-full-debug --enable-redirect-malloc
> > --enable-threads=pthr
> > eads
> > and linked the program with .libs/libgc.a.
> > The program gets first
> > signal SIGPWR, Power fail/restart
> > and then
> > signal SIGXCPU, CPU time limit exceeded
> > What can I do?
> > -- Beppe
> > _______________________________________________
> > Gc mailing list
> > Gc@linux.hpl.hp.com
> > https://linux.hpl.hp.com/cgi-bin/mailman/listinfo/gc
> Gc mailing list