[Top][All Lists]

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: Debugging ghc6: Was: Re: Failure: ghc ...

From: Samuel Thibault
Subject: Re: Debugging ghc6: Was: Re: Failure: ghc ...
Date: Thu, 14 Apr 2011 15:30:45 +0200
User-agent: Mutt/1.5.12-2006-07-14

Svante Signell, le Thu 14 Apr 2011 15:22:19 +0200, a écrit :
> On Thu, 2011-04-14 at 15:07 +0200, Samuel Thibault wrote:
> > > I'm not fluent with the pflocal/libpipe code.
> > 
> > I'm not either, and I don't think anybody on the list is really. Dive
> > into the code, understand it, etc.... the usual stuff when debugging
> > something that isn't your own code.
> OK, some remaining questions you probably can answer directly:
> 1) Using watchpoints or breakpoints or??

These would block your pflocal and make the box unusable. Also, you
don't really know where to put them, so you first have to investigate
from the point where ghc is hung, by looking at the state of the threads
which are answering the RPCs from ghc.

> 2) Can I set a break/watchpoint in a .h-file?

The whole point of inline functions is that they are inlined in several
places, so I doubt gdb supports it.

> 3) Found SIGPIPE in libpthread/signal/: interesting or not?

The code is just reaction to SIGPIPE: sig_terminate. So it's not the

> 4) Found EPIPE in libpipe/, pflocal/, libftpconn/: last one not
> interesting?

libftpconn is only for ftpfs, nothing to do here.

> 5) Other??



reply via email to

[Prev in Thread] Current Thread [Next in Thread]