Hi all,
Here's an update. While playing with some parameters I managed to
produce a case where compilation still fails, but this time with an
assertion error instead of a segfault:
... snipped ...
[112 of 202] Compiling System.Posix.Types ( System/Posix/Types.hs,
Please record the repro steps exactly, including the git hashes of any
repositories that you use. If it is a GC bug, the last thing we want is
for it to disappear, because then we lose the opportunity to find it.
If you could put the build steps into a script that we can run to
reproduce the
Oops last time I checked I hadn't cherry-picked the #9078 fix. Retested
with that and it still segfaults.
Unfortunately we haven't found a smaller test case yet. We've been using
Vagrant for repeatable test runs for GHCJS in the past. Would a Vagrant
script for reproducing the crash be ok?
luite
On Thu, May 29, 2014 at 5:41 PM, Simon Marlow marlo...@gmail.com wrote:
Yeah, vagrant would be fine.
Do you have any FFI or other strange things in GHCJS that might
conceivably cause this?
Not in GHCJS itself as far as I know, but its dependency list is rather
long, unfortunately.
luite
Hi all,
I'm suffering from a RTS bug(probably GC related) that makes making
progress in my GSoC project impossible. I have very limited knowledge
of GHC internals and I currently have no idea how to produce a minimal
program that demonstrates the bug. I wrote how to reproduce it and gdb
backtrace
There are a couple of recent GC-related bug fixes (#9045 and #9001). Before
trying to track this down any further I suggest you try using the tip of
the ghc-7.8 branch with commit fc0ed8a730 cherry-picked on top.
Regards,
Reid Barton
On Wed, May 28, 2014 at 6:04 AM, Ömer Sinan Ağacan
I did that yesterday but it still segfaulted in the same place.
luite
On Wed, May 28, 2014 at 7:43 PM, Reid Barton rwbar...@gmail.com wrote:
There are a couple of recent GC-related bug fixes (#9045 and #9001).
Before trying to track this down any further I suggest you try using the
tip of
Hey Ömer,
As a first guess, there were a few known segfaults fixed in the ghc-7.8
branch. Have you tried building GHCJS using this branch? Could be one
of these three:
https://ghc.haskell.org/trac/ghc/ticket/9001
https://ghc.haskell.org/trac/ghc/ticket/9045
