"+RTS -A" parameter and CPU cache size

2006-06-14 Thread Bulat Ziganshin
Hello glasgow-haskell-users, "+RTS -A" parameter sets up size of memory allocation area. by default it set to 256kb and this means that after each 256 kb allocated minor GC occurs and data from this block that is still alive are moved to main heap area (what is scanned only on major GCs) while re

RE: Any way to catch runtime errors in a DLL?

2006-06-14 Thread Simon Peyton-Jones
I've added this qn and reply to the GHC FAQ http://haskell.org/haskellwiki/GHC/FAQ#The_Foreign_Function_Interface | -Original Message- | From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] | On Behalf Of Simon Marlow | Sent: 14 June 2006 11:19 | To: Michael Marte | Cc: GHC Users Mai

Re: Any way to catch runtime errors in a DLL?

2006-06-14 Thread Simon Marlow
Michael Marte wrote: if a runtime error occurs inside a DLL compiled by ghc (like "irrefutable pattern match failed" or exceptions caused by error), the application that called the DLL function dies. This is ok for development but unacceptable when it happens with a user sitting in front of th

Re: Any way to catch runtime errors in a DLL?

2006-06-14 Thread Bulat Ziganshin
Hello Michael, Wednesday, June 14, 2006, 12:41:59 PM, you wrote: > if a runtime error occurs inside a DLL compiled by ghc (like > "irrefutable pattern match failed" or exceptions caused by error), see setUncaughtExceptionHandler in module Control.Exception and module GHC.ConsoleHandler - _may be

Re: Solaris x86 package

2006-06-14 Thread Christian Maeder
Georg Sauthoff schrieb: > After a break I built the project again - and it failed (everytime > segfaults). > > Thus I guess that I have problems with the threaded rts (which are more > difficult too reproduce, than the previous ones). > > Ah, and ghci segfaults every time - I didn't test ghci bef

Any way to catch runtime errors in a DLL?

2006-06-14 Thread Michael Marte
Hello *, if a runtime error occurs inside a DLL compiled by ghc (like "irrefutable pattern match failed" or exceptions caused by error), the application that called the DLL function dies. This is ok for development but unacceptable when it happens with a user sitting in front of the display. (