Date: Thu, 10 Aug 2006 16:26:18 -0400 (EDT) From: Daniel Eischen <deischen@freebsd.org> To: Simon Marlow <simonmar@microsoft.com> Cc: glasgow-haskell-users@haskell.org, haskell@freebsd.org, Volker Stolz <vs@foldr.org>, Simon Peyton-Jones <simonpj@microsoft.com>, Tony Finch <dot@dotat.at>, Robert Watson <rwatson@freebsd.org>, threads@freebsd.org Subject: RE: GHC 6.4.3 on FreeBSD (fwd) Message-ID: <Pine.GSO.4.64.0608101624050.23461@sea.ntplx.net> In-Reply-To: <2E9B33CE230409489A7ED37E5E34090F05148C80@EUR-MSG-20.europe.corp.microsoft.com> References: <2E9B33CE230409489A7ED37E5E34090F05148C80@EUR-MSG-20.europe.corp.microsoft.com>
next in thread | previous in thread | raw e-mail | index | archive | help
On Thu, 10 Aug 2006, Simon Marlow wrote: > Dear threads@freebsd.org (and others), > > This is relating to the problems we're experiencing with GHC's threaded > runtime on FreeBSD (see context below). > > GHC itself, which is a Haskell program, when compiled with itself and > linked against GHC's threaded runtime, sometimes hangs eating 100% CPU. > This happens when it is linked with -pthreads, I haven't seen it when > linking with -lthr. > > If I attach using gdb to a hung process, I see this: > > (gdb) where > #0 0x2897146b in pthread_testcancel () from /usr/lib/libpthread.so.2 > #1 0x28972499 in __error () from /usr/lib/libpthread.so.2 > #2 0x2895e6ba in sigaction () from /usr/lib/libpthread.so.2 > #3 0x087ea6b4 in runProcess (args=0x29091758, workingDirectory=0x0, > environment=0x0, > fdStdInput=0, fdStdOutput=1, fdStdError=2, set_inthandler=1, > inthandler=0, > set_quithandler=1, quithandler=0) at runProcess.c:61 > #4 0x0879b3d0 in s3ja_info () That trace isn't possible. I've found that you can't trust these traces unless you compile libpthread with "-g". -- DE
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?Pine.GSO.4.64.0608101624050.23461>