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
How hard *would* it be to replace the global weak pointer lock with
something that scales better?
I'm looking at switching some of my older BDD code into Haskell.
To do so I'd love to be able to use an intuitive weak-pointer based cache
management scheme, but I have to confess the notion of a
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
Yes, this should be easy to fix, it just hasn't been done.
Edward
Excerpts from Carter Schonwald's message of 2014-05-28 11:21:30 -0700:
@Edwardk, ezyang has a ticket on this very topic!
https://ghc.haskell.org/trac/ghc/ticket/9075
(is that what you're thinking?)
On Wed, May 28, 2014 at
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
