On Thu, May 08, 2025 at 09:11:12AM +0000, Klemens Nanni wrote: > 08.05.2025 11:50, Anthony J. Bentley пишет: > > The stack dump was disabled by kn's recent commit, but I doubt that > > caused this crash. It's very annoying that rtorrent neither prints a > > stack trace nor leaves a corefile behind though, can we fix that? > > I only disabled libexecinfo since it wasn't explicitly required/enabled, > feel free to enable it if that makes a difference, although I'd probably > (first) look into why there are no core dumps, though.
Well, libexecinfo is in base now, so I don't see why you're explicitely disabling it. 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? -- jca
