Closed #493.
--
You are receiving this because you are subscribed to this thread.
Reply to this email directly or view it on GitHub:
https://github.com/rpm-software-management/rpm/issues/493#event-1800049896___
Rpm-maint mailing list
Rpm-maint@lists.rpm
The libc manual supplies example code.
Determining what signals constitute an "abnormal exit" where an immediate
backtrace might be useful is left to maintainers. I have listed some usage
cases that I believe n immediate backtrace would be useful.
Surely you are aware of the often reported rpmd
If you have patch - please submit PR.
--
You are receiving this because you are subscribed to this thread.
Reply to this email directly or view it on GitHub:
https://github.com/rpm-software-management/rpm/issues/493#issuecomment-412346540___
Rpm-maint m
Glibc provides a routine to unwind the stack (including symbols when available
iirc). This RFE is a suggestion to display the stack when exiting abnormally on
certain signals.
RPM -- and an rpmdb in particular -- is expected to Just Work in spite of
* itchy trigger fingers using 'kill -9' when r
