19 Dec
2016
19 Dec
'16
2:07 p.m.
Andrey Semashev wrote:
Yes, if the only way to do that is fork+exec then that is not usable for me, not as the default implementation of the stacktrace decoding algorithm. If such functionality is provided, it should be strictly optional and disabled by default (i.e. on Windows don't start the helper process unless the user explicitly requests that in runtime). Let the decoding algorithm itself be not-signal-safe but in-process.
Why is spawning a process to do the decoding unacceptable? I'm sorry if you already explained this in a previous message.