kicad-developers team mailing list archive
-
kicad-developers team
-
Mailing list archive
-
Message #37535
Re: [PATCH] Print stacktrace when SIGSEGV or SIGABRT appears
Thomas,
Is there some reason you did not use wxDebugReport[1]? This would hide
the platform dependent issues and make for much cleaner code.
Cheers,
Wayne
[1]: https://docs.wxwidgets.org/3.0/classwx_debug_report.html
On 9/19/2018 12:38 PM, Thomas Pointhuber wrote:
> Hi,
>
> I wrote some basic crash-handler based on signal handler code published
> on the mailinglist some time ago:
>
> * https://lists.launchpad.net/kicad-developers/msg27148.html
>
> For now, it uses the glibc backtrace function to print a basic
> stack-trace onto the console, and if possible a crash dump file in the
> current working directory.
>
> Unfortunately printing pretty stack-traces is not easy, which means at
> the moment users need to manually prettify them when required. To do
> this the tools addr2line and c++filt can be used to find the actual
> location of the crash.
>
> Nevertheless, it is better than nothing at all. And it could be
> especially helpful to find rare crashes which are hard to reproduce.
>
> Regards, Thomas
>
>
> _______________________________________________
> Mailing list: https://launchpad.net/~kicad-developers
> Post to : kicad-developers@xxxxxxxxxxxxxxxxxxx
> Unsubscribe : https://launchpad.net/~kicad-developers
> More help : https://help.launchpad.net/ListHelp
>
References