1berry/ruby
1
0
Fork 0
Code Issues Packages Projects Releases Wiki Activity

Don't clear cfp, it causes problems.

Browse Source
This commit is contained in:
Samuel Williams 2019-06-20 14:55:43 +12:00
parent 15c4f6aed2
commit 7d9d1ed463
2 changed files with 3 additions and 6 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

7
thread.c
View File

@ -599,11 +599,8 @@ thread_cleanup_func_before_exec(void *th_ptr)
// The thread stack doesn't exist in the forked process:
th->ec->machine.stack_start = th->ec->machine.stack_end = NULL;
// Appears to be causing a lot of issues.
if (0) {
// The vm_stack is `alloca`ed on the thread stack, so it's gone too:
rb_ec_clear_vm_stack(th->ec);
}
// The vm_stack is `alloca`ed on the thread stack, so it's gone too:
rb_ec_clear_vm_stack(th->ec);
}
static void

2
vm.c
View File

@ -2714,7 +2714,7 @@ rb_ec_clear_vm_stack(rb_execution_context_t *ec)
rb_ec_set_vm_stack(ec, NULL, 0);
// Avoid dangling pointers:
ec->cfp = NULL;
// ec->cfp = NULL;
}
static void