suzanne.soy/racket
1
0
Fork 0
Code Issues Pull Requests Actions Packages Projects Releases Wiki Activity

fix xform-related bug triggered by making atomic timeout place-local

Browse Source
This commit is contained in:
Matthew Flatt 2011-11-22 05:49:12 -07:00
parent 6784007206
commit cc1b7bb8b4
1 changed files with 6 additions and 1 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

7
src/racket/src/thread.c
View File

@ -4342,6 +4342,7 @@ static void call_on_atomic_timeout(int must)
Scheme_Kill_Action_Func private_on_kill; Scheme_Kill_Action_Func private_on_kill;
void *private_kill_data; void *private_kill_data;
void **private_kill_next; void **private_kill_next;
Scheme_On_Atomic_Timeout_Proc oat;
/* Save any state that has to do with the thread blocking or /* Save any state that has to do with the thread blocking or
sleeping, in case on_atomic_timeout() runs Racket code. */ sleeping, in case on_atomic_timeout() runs Racket code. */
@ -4364,7 +4365,11 @@ static void call_on_atomic_timeout(int must)
p->block_check = NULL; p->block_check = NULL;
p->block_needs_wakeup = NULL; p->block_needs_wakeup = NULL;
on_atomic_timeout(must); /* When on_atomic_timeout is thread-local, need a
local variable so that the function call isn't
obscured to xform: */
oat = on_atomic_timeout;
oat(must);
p->running = running; p->running = running;
p->sleep_end = sleep_end; p->sleep_end = sleep_end;