#367: Infinite loops can hang Concurrent Haskell
------------------------------------------+---------------------------------
Reporter: simonpj | Owner:
Type: bug | Status: new
Priority: lowest | Milestone: _|_
Component: Compiler | Version: 6.4.1
Resolution: None | Keywords: scheduler
allocation
Os: Unknown/Multiple | Architecture: Unknown/Multiple
Failure: Incorrect result at runtime | Difficulty: Unknown
Testcase: | Blockedby:
Blocking: | Related:
------------------------------------------+---------------------------------
Comment(by ezyang):
Alas, the above proposal is totally infeasible in the current world order,
because it is completely impossible to run Haskell code without holding
the capability. I thought you might get away with only instrumenting GC
calls, but really any and all of the memory you're looking at could get
moved around by a GC who thinks that they have all the capabilities. So
we’re back to an implementation strategy where a thread holding a
capability gets killed, and then we recover, but this seems generally
Hard(TM).
--
Ticket URL: <http://hackage.haskell.org/trac/ghc/ticket/367#comment:16>
GHC <http://www.haskell.org/ghc/>
The Glasgow Haskell Compiler
_______________________________________________
Glasgow-haskell-bugs mailing list
Glasgow-haskell-bugs@haskell.org
http://www.haskell.org/mailman/listinfo/glasgow-haskell-bugs
