4 ms·
Yeah, unless you have a very specific architecture and compiler, etc., in mind. "Handling" SIGSEGV is madness -- you're usually already deep in UB territory if
by Quekid5 3y ago
Yeah, unless you have a very specific architecture and compiler, etc., in mind. "Handling" SIGSEGV is madness -- you're usually already deep in UB territory if a SIGSEGV happens.
Re: Your use case, I believe the most recent C++ standard has a portable way to do stack traces, so yay!