[project @ 2002-02-15 14:49:08 by simonmar]
authorsimonmar <unknown>
Fri, 15 Feb 2002 14:49:08 +0000 (14:49 +0000)
committersimonmar <unknown>
Fri, 15 Feb 2002 14:49:08 +0000 (14:49 +0000)
commit93d2b95262b16f63043a01804991f3248d6867d7
treea9a1e0692f945ed9e6f064f5a7cce26c29389506
parent5b50dc399fc77ef900e69a6262ec8fc5232575da
[project @ 2002-02-15 14:49:08 by simonmar]
Fix bugs in async exception raising: instead of trying to build an
application of the exception handler to the exception directly, just
leave a THUNK(raise,exception) on top of the CATCH_FRAME ready to
trigger the next time this thread is run.

This avoids two problems: the PAP we were using before wasn't really a
PAP, which broke some assumptions elsewhere (c.f. PAP_ENTRY:
CATCH_FRAME failure), and there was also some duplication between
raiseAsync and raisezh_fast due to the fact that we were attempting to
do the raising directly.
ghc/rts/Schedule.c