I'm implementing some kind of ruby extension (in fact, I'm embedding Ruby into a C/C++ application), and I'm getting the following error:
<SystemStackError: stack level too deep>
when calling to module_eval
The error gets thrown randomly, only after updating 2.3 to 2.5, any ideas how to debug it?
I've seen that set_trace_func can be used for that purpose, am I correct?
there is also a initial error in ruby_init which overwrites the stack, I found it by means of valgrind, this didn't happen before, and maybe it is because of stack protector flag but I'm not sure
any help would be highly appreciated