On Fri, Mar 15, 2013 at 5:17 PM, Edward Z. Yang <[email protected]> wrote: > There is a lot of subtlety in this space, largely derived from the > complexity of interpreting GHC's current profiling information. Your > questions, comments and suggestions are greatly appreciated!
How secure is this? One of the reasons for forking a process and then killing it after a timeout in lambdabot/mueval is because a thread can apparently block the GC from running with a tight enough loop and the normal in-GHC method of killing threads doesn't work. Can one simultaneously in a thread allocate ever more memory and suppress kill signals? -- gwern http://www.gwern.net _______________________________________________ Haskell-Cafe mailing list [email protected] http://www.haskell.org/mailman/listinfo/haskell-cafe
