From: Claus R. <cla...@ta...> - 2004-08-04 13:38:24
|
I've now managed to get one of the problems in a reproducable form (windows 98, ghc-6.2.1, wxhaskell-0.8): 1. start ghci 2. :cd <...>/wxhaskell-0.8/samples/wx 3. :set -package wx 4. :l Process 5. main in Process window: 6. ghci 7. :q 8. ghci 9. :q that seems to lock up my system, with optional bluescreen (sometimes it needs three iterations instead of two). doing the equivalent under cygwin (using System.system instead of wxhaskell's Process) doesn't seem to suffer from the same problem, so it can't be (just) ghc's fault. Cheers, Claus |
From: Daan L. <daa...@xs...> - 2004-08-04 15:47:30
|
Claus Reinke wrote: >I've now managed to get one of the problems in a >reproducable form (windows 98, ghc-6.2.1, wxhaskell-0.8): > > Thanks, I look into it in more detail when I get back from holidays (= next week). -- Daan. >1. start ghci >2. :cd <...>/wxhaskell-0.8/samples/wx >3. :set -package wx >4. :l Process >5. main > >in Process window: > >6. ghci >7. :q >8. ghci >9. :q > >that seems to lock up my system, with optional bluescreen >(sometimes it needs three iterations instead of two). > >doing the equivalent under cygwin (using System.system >instead of wxhaskell's Process) doesn't seem to suffer from >the same problem, so it can't be (just) ghc's fault. > >Cheers, >Claus > > > >------------------------------------------------------- >This SF.Net email is sponsored by OSTG. Have you noticed the changes on >Linux.com, ITManagersJournal and NewsForge in the past few weeks? Now, >one more big change to announce. We are now OSTG- Open Source Technology >Group. Come see the changes on the new OSTG site. www.ostg.com >_______________________________________________ >wxhaskell-users mailing list >wxh...@li... >https://lists.sourceforge.net/lists/listinfo/wxhaskell-users > > > > |