Duplicate the entire stack (backtrace) during coroutine creation, store the RBP in the jmpbuf, and replicate the parent RBP and stack home space containing local variables from the parent function.
Keep in mind that local variables might be freed after coroutine creation and should be freed while the coroutine is running. Please be caution with these variables; they only serve as backtrace hints and do not guarantee the validity of all local variables.
This Pull Request primarily serves as a helpful debugging tool for tracking the stack, with limited but valuable utility, particularly for identifying the creators of the current coroutine.
I have tested it in cygwin, before this patch, the backtrace is bellow:
(gdb) bt
#0 pfn (arg=0x0) at backtrace.cpp:9
#1 0x0000000100401cea in _st_thread_main () at sched.c:380
#2 0x000000010040265f in st_thread_create (start=0x7ffffcbc0, arg=0x100401b0d <st_thread_exit+588>, joinable=19616, stk_size=131072) at sched.c:666
Backtrace stopped: previous frame inner to this frame (corrupt stack?)
After this patch, the backtrace is:
(gdb) bt
#0 pfn (arg=0x0) at backtrace.cpp:9
#1 0x0000000100401cea in _st_thread_main () at sched.c:380
#2 0x00000001004027f0 in st_thread_create (start=0x100401080 <pfn(void*)>, arg=0x0, joinable=0, stk_size=131072) at sched.c:698
#3 0x00000001004010d2 in bar (argc=0) at backtrace.cpp:16
#4 0x00000001004010f1 in foo (argc=0) at backtrace.cpp:21
Backtrace stopped: previous frame inner to this frame (corrupt stack?)
Because only save the parent RBP, so only trace some levels of backtrace.
Duplicate the entire stack (backtrace) during coroutine creation, store the RBP in the jmpbuf, and replicate the parent RBP and stack home space containing local variables from the parent function.
Keep in mind that local variables might be freed after coroutine creation and should be freed while the coroutine is running. Please be caution with these variables; they only serve as backtrace hints and do not guarantee the validity of all local variables.
This Pull Request primarily serves as a helpful debugging tool for tracking the stack, with limited but valuable utility, particularly for identifying the creators of the current coroutine.
I have tested it in cygwin, before this patch, the backtrace is bellow:
After this patch, the backtrace is:
Because only save the parent RBP, so only trace some levels of backtrace.