Re: [GHC] #985: Memory Leak in freeHaskellFunPtr

[GHC]

#985: Memory Leak in freeHaskellFunPtr
--+-
 Reporter:  [EMAIL PROTECTED]|  Owner:  igloo   
 Type:  merge | Status:  closed  
 Priority:  normal|  Milestone:  6.6.1   
Component:  Compiler  |Version:  6.6 
 Severity:  normal| Resolution:  fixed   
 Keywords:  callback, FFI, freeHaskellFunPtr  | Difficulty:  Unknown 
 Testcase:  provided  |   Architecture:  Multiple
   Os:  Windows   |  
--+-
Changes (by igloo):

  * resolution:  => fixed
  * status:  new => closed

Comment:

 Merged.

-- 
Ticket URL: 
GHC 
The Glasgow Haskell Compiler___
Glasgow-haskell-bugs mailing list
Glasgow-haskell-bugs@haskell.org
http://www.haskell.org/mailman/listinfo/glasgow-haskell-bugs

Re: [GHC] #985: Memory Leak in freeHaskellFunPtr

[Ian Lynagh]

On Sat, Feb 03, 2007 at 01:04:41PM +0100, Sven Panne wrote:
> Am Donnerstag, 1. Februar 2007 14:56 schrieb GHC:
> >
> >  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.

I haven't seen it anywhere; I think Simon forgot to push it (either that
or I'm just being dopier than normal).

> Is there an automatic way to see which patches 
> should still be merged into which direction?

The http://cvs.haskell.org/trac/ghc/wiki/6.6_Branch page describes how
to check that there are no patches in 6.6 only that should be in the
HEAD (although I haven't been actively keeping the list of exceptions
up-to-date; I think it'll be easier to do a bulk update when checking
that the HEAD is not missing anything, as there shouldn't be many new
patches missing from the head, and most of them should be called
"MERGED.*").

For patches in the HEAD that should be in 6.6, the number of exceptions
would make the same system impractical. To make sure a patch doesn't get
missed, open a trac ticket of type "merge" and put the patch name in it.
(Noting that it should be merged in the patch description or sending an
e-mail to ask for it to be merged are also OK, but obviously if I miss
them then there is no easy way of noticing).


Thanks
Ian

___
Glasgow-haskell-bugs mailing list
Glasgow-haskell-bugs@haskell.org
http://www.haskell.org/mailman/listinfo/glasgow-haskell-bugs

Re: [GHC] #985: Memory Leak in freeHaskellFunPtr

[Sven Panne]

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
Glasgow-haskell-bugs@haskell.org
http://www.haskell.org/mailman/listinfo/glasgow-haskell-bugs

Re: [GHC] #985: Memory Leak in freeHaskellFunPtr

[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)
 }}}

-- 
Ticket URL: 
GHC 
The Glasgow Haskell Compiler___
Glasgow-haskell-bugs mailing list
Glasgow-haskell-bugs@haskell.org
http://www.haskell.org/mailman/listinfo/glasgow-haskell-bugs

Re: [GHC] #985: Memory Leak in freeHaskellFunPtr

[GHC]

#985: Memory Leak in freeHaskellFunPtr
--+-
 Reporter:  [EMAIL PROTECTED]|  Owner:  simonmar
 Type:  bug   | 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

Comment:

 I'll look into this.

-- 
Ticket URL: 
GHC 
The Glasgow Haskell Compiler___
Glasgow-haskell-bugs mailing list
Glasgow-haskell-bugs@haskell.org
http://www.haskell.org/mailman/listinfo/glasgow-haskell-bugs

Re: [GHC] #985: Memory Leak in freeHaskellFunPtr

[GHC]

#985: Memory Leak in freeHaskellFunPtr
--+-
 Reporter:  [EMAIL PROTECTED]|  Owner:  
 Type:  bug   | 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 igloo):

  * milestone:  => 6.6.1

Comment:

 The leak, but not the garbage, happens for me on Linux/amd64.

-- 
Ticket URL: 
GHC 
The Glasgow Haskell Compiler___
Glasgow-haskell-bugs mailing list
Glasgow-haskell-bugs@haskell.org
http://www.haskell.org/mailman/listinfo/glasgow-haskell-bugs

Re: [GHC] #985: Memory Leak in freeHaskellFunPtr

[GHC]

#985: Memory Leak in freeHaskellFunPtr
--+-
 Reporter:  [EMAIL PROTECTED]|  Owner:  
 Type:  bug   | Status:  new 
 Priority:  normal|  Milestone:  
Component:  Compiler  |Version:  6.6 
 Severity:  normal| Resolution:  
 Keywords:  callback, FFI, freeHaskellFunPtr  | Difficulty:  Unknown 
 Testcase:  provided  |   Architecture:  Multiple
   Os:  Windows   |  
--+-
Comment (by simonpj):

 Matthew adds (later email): by the way, why can't I get the callback to
 actually work in
 this example?  If I for example uncomment the line
 {{{
 -- pd <- cfunc pcf
 }}}
 and say print out the value of `pd`,  I get garbage values.

 Should I have used `CDouble`?  I think for windows `HsDouble` = double in
 C
 land.

-- 
Ticket URL: 
GHC 
The Glasgow Haskell Compiler___
Glasgow-haskell-bugs mailing list
Glasgow-haskell-bugs@haskell.org
http://www.haskell.org/mailman/listinfo/glasgow-haskell-bugs