09.05.2025 15:17, Jeremie Courreges-Anglas пишет: > Well, libexecinfo is in base now, so I don't see why you're > explicitely disabling it.
Because my brain was stuck in "libexecinfo is ports" land. > The reason why there no core dumps is probably due to the explicit > signal handling for SIGSEGV and friends. Code that explicitely uses > libexecinfo to show stack traces often don't disarm their signal > handler and then raise() the caught signal. > > We could disable that the code that sets up some signal handlers, but > why not just re-enable libexecinfo and see whether it prints a useful > stack trace? I reenabled it for both lib and cli ports, thanks for the hint.
