Am Donnerstag, 1. Februar 2007 14:56 schrieb GHC:
> #985: Memory Leak in freeHaskellFunPtr
> ----------------------------------------------+----------------------------
>- Reporter: [EMAIL PROTECTED] | Owner: igloo
> Type: merge | Status: new Priority:
> normal | Milestone: 6.6.1 Component:
> Compiler | Version: 6.6 Severity: normal
> | Resolution:
> Keywords: callback, FFI, freeHaskellFunPtr | Difficulty: Unknown
> Testcase: provided | Architecture: Multiple
> Os: Windows |
> ----------------------------------------------+----------------------------
>- Changes (by simonmar):
>
> * owner: simonmar => igloo
> * type: bug => merge
>
> Comment:
>
> Fixed. Patch to merge (from 6.6 to HEAD):
>
> {{{
> Thu Feb 1 13:53:33 GMT 2007 Simon Marlow <[EMAIL PROTECTED]>
> * fix memory leak in allocExec/freeExec (see bug #985)
> }}}
Hmmm, I think I haven't seen this patch in the HEAD yet. In general: The
current quite liberal (a.k.a. chaotic :-) ) style where patches are
somtetimes applied to STABLE first and merged to HEAD later and vice versa
gives me some headaches. In good old times we fixed the HEAD and simply
merged this to STABLE. :-( Is there an automatic way to see which patches
should still be merged into which direction? If not, we should handle things
a bit stricter, I guess...
Cheers,
S.
_______________________________________________
Glasgow-haskell-bugs mailing list
[email protected]
http://www.haskell.org/mailman/listinfo/glasgow-haskell-bugs
