summaryrefslogtreecommitdiff
path: root/rts/Schedule.h
diff options
context:
space:
mode:
authorSimon Marlow <simonmar@microsoft.com>2007-07-24 15:30:57 +0000
committerSimon Marlow <simonmar@microsoft.com>2007-07-24 15:30:57 +0000
commit681aad99cb29ce54f72ec2a916fb1aab0fa0fabb (patch)
tree65e13d3bc1acad8b859e63886c5e5ea429f7236f /rts/Schedule.h
parent1bd1fb932375bc4b065cc8de23f0d251e8075395 (diff)
downloadhaskell-681aad99cb29ce54f72ec2a916fb1aab0fa0fabb.tar.gz
hs_exit()/shutdownHaskell(): wait for outstanding foreign calls to complete before returning
This is pertinent to #1177. When shutting down a DLL, we need to be sure that there are no OS threads that can return to the code that we are about to unload, and previously the threaded RTS was unsafe in this respect. When exiting a standalone program we don't have to be quite so paranoid: all the code will disappear at the same time as any running threads. Happily exiting a program happens via a different path: shutdownHaskellAndExit(). If we're about to exit(), then there's no need to wait for foreign calls to complete.
Diffstat (limited to 'rts/Schedule.h')
-rw-r--r--rts/Schedule.h2
1 files changed, 1 insertions, 1 deletions
diff --git a/rts/Schedule.h b/rts/Schedule.h
index ba5efc29ad..ddac92be4b 100644
--- a/rts/Schedule.h
+++ b/rts/Schedule.h
@@ -18,7 +18,7 @@
* Locks assumed : none
*/
void initScheduler (void);
-void exitScheduler (void);
+void exitScheduler (rtsBool wait_foreign);
void freeScheduler (void);
// Place a new thread on the run queue of the current Capability