On Wed, 2007-02-28 at 09:32 -0800, David Brown wrote:
> However, what I missed is that the hsc2hs target files are placed
> alongside the source, not in the dist directory. I had been building
> zlib on x86 using the hs generated on an amd64 machine. The offsets
> in the structures were wrong.
David Brown wrote:
> Hmm. I recompiled 'zlib' with some extra tracing and now the problem
> doesn't happen. Even without the tracing it is fine. Must have been
> something wrong with the compiled library. Scary. But, everything is
> working fine now.
I figured out what the problem is. I've
David Brown wrote:
> I discovered it isn't just x86, but appears to be this particular
> machine. My other machines work fine. There might be a library
> difference between the machines, or something like that.
Program received signal SIGSEGV, Segmentation fault.
[Switching to Thread -121
Simon Marlow wrote:
> David Brown wrote:
>
>> 0x080b45b8 in s2EI_info ()
>
> Fortunately I wrote a wiki page on just this subject, mainly so that
> I can say RTFM :-) After reading the FM, if you're still having
> difficulties then post a followup and we'll try to help if we can.
>
> http:/
Simon Marlow <[EMAIL PROTECTED]> writes:
> Fortunately I wrote a wiki page on just this subject, mainly so that I
> can say RTFM :-) After reading the FM, if you're still having
> difficulties then post a followup and we'll try to help if we can.
>
>http://hackage.haskell.org/trac/ghc/wiki/De
David Brown wrote:
I'm developing a program with GHC-6.6. I've been on amd64, and
haven't had problems, but now when I run the program on on x86 (after
cleaning and recompiling), I'm getting a segfault.
gdb isn't very helpful at all:
Program received signal SIGSEGV, Segmentation fault.
I'm developing a program with GHC-6.6. I've been on amd64, and
haven't had problems, but now when I run the program on on x86 (after
cleaning and recompiling), I'm getting a segfault.
gdb isn't very helpful at all:
Program received signal SIGSEGV, Segmentation fault.
[Switching to Thread
