From d3b1f0b627ccc6705d9fe958549badb87a74ded1 Mon Sep 17 00:00:00 2001
From: Paul Sokolovsky
Date: Fri, 29 Jan 2016 01:05:53 +0200
Subject: py/runtime: mp_stack_ctrl_init() should be called immediately on
 startup.

Calling it from mp_init() is too late for some ports (like Unix), and leads
to incomplete stack frame being captured, with following GC issues. So, now
each port should call mp_stack_ctrl_init() on its own, ASAP after startup,
and taking special precautions so it really was called before stack variables
get allocated (because if such variable with a pointer is missed, it may lead
to over-collecting (typical symptom is segfaulting)).
---
 py/runtime.c | 1 -
 1 file changed, 1 deletion(-)

(limited to 'py')

diff --git a/py/runtime.c b/py/runtime.c
index b0f407a15..e4a4d5b3f 100644
--- a/py/runtime.c
+++ b/py/runtime.c
@@ -61,7 +61,6 @@ const mp_obj_module_t mp_module___main__ = {
 
 void mp_init(void) {
     qstr_init();
-    mp_stack_ctrl_init();
 
     // no pending exceptions to start with
     MP_STATE_VM(mp_pending_exception) = MP_OBJ_NULL;
-- 
cgit v1.2.3