Re: Bug in GC's ordering of ForeignPtr finalization?

2011-08-29 Thread Bertram Felgenhauer
Dear Ben, Ben Gamari wrote: > After looking into this issue in a bit more depth, I'm even more > confused. In fact, I would not be surprised if I have stumbled into a > bug in the GC. [...] > MessagesMessage > | > | msmpp > \/ > QueryMe

Re: Bug in GC's ordering of ForeignPtr finalization?

2011-08-28 Thread Antoine Latter
On Sun, Aug 28, 2011 at 10:47 PM, Ben Gamari wrote: > On Sun, 28 Aug 2011 22:26:05 -0500, Antoine Latter wrote: >> One problem you might be running in to is that the optimization passes >> can notice that a function isn't using all of its arguments, and then >> it won't pass them. These even appl

Re: Bug in GC's ordering of ForeignPtr finalization?

2011-08-28 Thread Ben Gamari
On Sun, 28 Aug 2011 22:26:05 -0500, Antoine Latter wrote: > One problem you might be running in to is that the optimization passes > can notice that a function isn't using all of its arguments, and then > it won't pass them. These even applies if the arguments are bound > together in a record type

Re: Bug in GC's ordering of ForeignPtr finalization?

2011-08-28 Thread Antoine Latter
On Sun, Aug 28, 2011 at 4:27 PM, Ben Gamari wrote: > On Tue, 16 Aug 2011 12:32:13 -0400, Ben Gamari wrote: >> It seems that the notmuch-haskell bindings (version 0.2.2 built against >> notmuch from git master; passes notmuch-test) aren't dealing with memory >> management properly. In particular,

Bug in GC's ordering of ForeignPtr finalization?

2011-08-28 Thread Ben Gamari
On Tue, 16 Aug 2011 12:32:13 -0400, Ben Gamari wrote: > It seems that the notmuch-haskell bindings (version 0.2.2 built against > notmuch from git master; passes notmuch-test) aren't dealing with memory > management properly. In particular, the attached test code[1] causes > talloc to abort. Unfo