Both methods cause the program to work as expected (just out of curiousity, how does this change how the program functions?)
Not sure if it still helps still but the gdb disassemble of the segfault shows
=> 0x00000000006adea1 <+33>: movsbq (%r14),%rax
with r14 containing 0
being the segfault line (after the function has been called ~21 times)
I could post the whole disassemble, if you need it.
Thanks a lot for helping out here, not being able to use ghci getting to be a pain.
Powered by Trac 0.11.1
By Edgewall Software.
Visit the Trac open source project athttp://trac.edgewall.org/