Re: ANNOUNCE: GHC 6.10.2 Release Candidate 1

2009-03-24 Thread jutaro

This is the first answer I got from the gtk2hs mailing list. Please consider
this issue seriously.
Jürgen


Axel Simon wrote:
 
 
 Phew,
 
 I think we're doomed. We have many, many little methods that take a  
 user-given function, wrap it into a foreign export wrapper which is  
 freed by using an on-destroy callback to Haskell. These functions are  
 most likely installed into some widgets (or other reference-counted  
 objects) that will be eventually destroyed by the Haskell garbage  
 collector. So, basically, we can't easily change Gtk2Hs. It will  
 involve many modifications. I can understand that not allowing  
 callbacks during GC is a great simplification in the runtime but it  
 seemed to be common practice to free Stable and function pointers  
 from within Haskell using a callback.
 
 So, unless I'm wrong on why finalizers call back into Haskell land,  
 then this means that Gtk2Hs is fundamentally broken for the  
 foreseeable future.
 
 Axel.
 

-- 
View this message in context: 
http://www.nabble.com/ANNOUNCE%3A-GHC-6.10.2-Release-Candidate-1-tp22524567p22691289.html
Sent from the Haskell - Glasgow-haskell-users mailing list archive at 
Nabble.com.

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


Re: ANNOUNCE: GHC 6.10.2 Release Candidate 1

2009-03-19 Thread jutaro

Hello Simon,
I've put a request about the issue on the gtk2hs users mailing list:

 I've tried a gtk2hs app on ghc 6.10.2 release candidate.
 It crashes frequently and Simon (as you can read down here) assumes it
 is gtk2hs problem.
 My question is:
Is this problem known to gtk2hs developers?
Is it really a gtk2hs problem?
How difficult is it to fix the problem?
When will we have a patch to use gtk2hs with 6.10.2, 
is it already in the repo?  

However, I'm a little surprised that a little version upgrade from 6.10.1 to
6.10.2 may break all gui apps based on gtk2hs. May it be that many more apps
are affected because of this change? What's about wxhaskell e.g.? Well,
maybe we have only few Haskell applications around, but usually I
wouldn't expect such a dramatic effect from such a moderate upgrade. Is this
fix so important to introduce it now? What does it help when it was never
officially supported if it causes such troubles?

Jürgen  
 


Simon Marlow-7 wrote:
 
 jutaro wrote:
 I've installed a GUI application based on gtk2hs.
 
 It frequently crashes with the error: 
 leksah: error: a C finalizer called back into Haskell.
 use Foreign.Concurrent.newForeignPtr for Haskell finalizers.
 
 This error did never occur with the 6.10 released version. It was
 verified
 that this happens on different machines. I've no idea how to isolate this
 bug.
 
 This will need to be fixed in gtk2hs.  Previously GHC allowed finalizers
 to 
 call back into Haskell, but this was never officially supported.  Now it
 is 
 officially unsupported, because finalizers created via
 Foreign.mkForeignPtr 
 are run directly by the garbage collector.
 
 See
 
   http://hackage.haskell.org/trac/ghc/ticket/1364
 
 Cheers,
   Simon
 ___
 Glasgow-haskell-users mailing list
 Glasgow-haskell-users@haskell.org
 http://www.haskell.org/mailman/listinfo/glasgow-haskell-users
 
 

-- 
View this message in context: 
http://www.nabble.com/ANNOUNCE%3A-GHC-6.10.2-Release-Candidate-1-tp22524567p22608413.html
Sent from the Haskell - Glasgow-haskell-users mailing list archive at 
Nabble.com.

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


Re: ANNOUNCE: GHC 6.10.2 Release Candidate 1

2009-03-18 Thread jutaro

I've installed a GUI application based on gtk2hs.

It frequently crashes with the error: 
leksah: error: a C finalizer called back into Haskell.
use Foreign.Concurrent.newForeignPtr for Haskell finalizers.

This error did never occur with the 6.10 released version. It was verified
that this happens on different machines. I've no idea how to isolate this
bug.

Any idea about this?
Jürgen Nicklisch-Franken  


Ian Lynagh wrote:
 
 
 We are pleased to announce the first release candidate for GHC 6.10.2:
 
 http://www.haskell.org/ghc/dist/6.10.2-rc1/
 
 This includes two source bundles:
 
 ghc-6.10.1.20090314-src.tar.bz2
 ghc-6.10.1.20090314-src-extralibs.tar.bz2
 
 Only the first of these is necessary. The extralibs package contains
 various extra packages that we normally supply with GHC - unpack the
 extralibs tarball on top of the source tree to add them, and they will
 be included in the build automatically.
 
 There are also installers for Windows (i386) and OS X (i386), and binary
 distributions for x86_64/Linux and i386/Linux. More may appear later.
 
 Please test as much as possible; bugs are much cheaper if we find them
 before the release!
 
 
 Thanks
 Ian, on behalf of the GHC team
 
 ___
 Glasgow-haskell-users mailing list
 Glasgow-haskell-users@haskell.org
 http://www.haskell.org/mailman/listinfo/glasgow-haskell-users
 
 

-- 
View this message in context: 
http://www.nabble.com/ANNOUNCE%3A-GHC-6.10.2-Release-Candidate-1-tp22524567p22592804.html
Sent from the Haskell - Glasgow-haskell-users mailing list archive at 
Nabble.com.

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