
If it's MacOS specific, we're not going to be much help at GHC HQ, because we don't have any (Macs that is). Wolfgang Thaller is the MacOS expert, but maybe there are others now? Simon | -----Original Message----- | From: Joel Reymont [mailto:joelr1@gmail.com] | Sent: 19 November 2005 00:57 | To: Simon Marlow | Cc: Simon Peyton-Jones; Haskell Cafe | Subject: Re: [Haskell-cafe] Project postmortem | | I'm happy to report that the problem can be reproduced by running the | code from my darcs repo at http://test.wagerlabs.com/postmortem. See | the README file. I'm on Mac OSX 10.4.3. | | The server just sits there, goes through the SSL handshake and... | does nothing else. The clients go through the handshake with the | server and do nothing else. The handshake goes through X number of | times and then the client crashes. | | On Nov 18, 2005, at 1:55 PM, Simon Marlow wrote: | | > How we normally proceed for a crash like this is as follows: examine | > where the crash happened and determine whether it is a result of | > heap or | > stack corruption, and then attempt to trace backwards to find out | > where | > the corruption originated from. Tracing backwards means running the | > program from the beginning again, so it's essential to have a | > reproducible example. Without reproducibility, we have to use a | > combination of debugging printfs and staring really hard at the code, | > which is much more time consuming (and still requires being able to | > run | > the program to make it crash with debugging output turned on).

Is Wolfgang still around? Would you guys be willing to guide me through this? I could then possibly become the next Mac OSX expert :-). I have the disassembler dumps, etc. I do not know how to approach this problem. I read up a bit on the GHC internals, STG, code generation, etc. Thanks, Joel P.S. Please feel free to take the email exchange offline, could be too boring for everyone else On Nov 21, 2005, at 9:35 AM, Simon Peyton-Jones wrote:
If it's MacOS specific, we're not going to be much help at GHC HQ, because we don't have any (Macs that is). Wolfgang Thaller is the MacOS expert, but maybe there are others now?

Simon, What about the non-OSX issue of using a Chan to collect traces from thousands of threads? It's not working very well for me when I use readChan in a loop (see the code). getChanContents works much better but then the logger thread is stuck forever and everything else that waits on it is stuck as well. The output from logger (Util.hs) stops after a few lines and thus memory taken starts to grow because all the output sent to the chan is not being processed. Thanks, Joel On Nov 21, 2005, at 9:35 AM, Simon Peyton-Jones wrote:
If it's MacOS specific, we're not going to be much help at GHC HQ, because we don't have any (Macs that is). Wolfgang Thaller is the MacOS expert, but maybe there are others now?
participants (2)
-
Joel Reymont
-
Simon Peyton-Jones