I just debugged a stack overflow on windows that was solved by increasing the stack size for all executables. Once #157 is solved this can be replaced with a value based on call graph analysis.
But we still have chkstck calling @panic. When this happens we try to dump a stack trace, but this uses the stack, which just overflowed. So this can't work. This could potentially be a use case for @newStackCall.
I just debugged a stack overflow on windows that was solved by increasing the stack size for all executables. Once #157 is solved this can be replaced with a value based on call graph analysis.
But we still have chkstck calling
@panic. When this happens we try to dump a stack trace, but this uses the stack, which just overflowed. So this can't work. This could potentially be a use case for@newStackCall.