Compiled code

2013-03-22 Thread migmit
Suppose I compiled some module and kept it's .hi and .o files. Is it possible to use this module in my program if the source code was deleted for some reason? Seems like the answer is "yes" — by creating a fake .hs file (with no real content) and touch-in .hi and .o files I tricked ghc so that i

Re: Strange behavior in GHC-compiled code

2012-05-26 Thread Mark Conway Wirt
On Fri, May 25, 2012 at 11:45:41PM +0200, Joachim Breitner wrote: > in that case I suggest you run a memory checker, e.g. memtest86, and see > if it find some hardware bugs. Or run the program on another machine and > see if the problem appears there as well. Hey Joachim, thanks for the referenc

Re: Strange behavior in GHC-compiled code

2012-05-25 Thread Joachim Breitner
Hi, Am Freitag, den 25.05.2012, 14:26 -0400 schrieb Mark Conway Wirt: > (I'm starting to think that this issue may not be related to > Haskell, as the problem arises so inconsistently -- sometimes the > code runs, sometimes it bombs out early. I haven't rebooted the > computer in a month or so, ma

Re: Strange behavior in GHC-compiled code

2012-05-25 Thread Mark Conway Wirt
On Fri, May 25, 2012 at 05:53:52PM +0100, Malcolm Wallace wrote: > Unless you show us the code, any answers will be guesses in the dark. > Does your program use unsafePerformIO unsafely perhaps? Or a version > of a library that happens to have a known bug? No unsafePerformIO's or IOrefs or the l

Re: Strange behavior in GHC-compiled code

2012-05-25 Thread Malcolm Wallace
Unless you show us the code, any answers will be guesses in the dark. Does your program use unsafePerformIO unsafely perhaps? Or a version of a library that happens to have a known bug? On 25/05/2012, at 14:33, Mark Conway Wirt wrote: > I have a piece of Haskell code that's been laying aroun

Strange behavior in GHC-compiled code

2012-05-25 Thread Mark Conway Wirt
Hi folks. I have a piece of Haskell code that's been laying around on my computer for about a year, and I recently decided to dust it off. The problem is that it used to work fine, but in the interim (in which I both upgraded OS versions/GHC versions and went from 32 bit to 64 bit) the code stopp