Hi, On 19.09.2018 18:38, Thomas Pointhuber wrote:
> 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. Then it needs to at least be made glibc specific. I'm not fond of these debugging aides inside programs, because IMO programs should do one thing and one thing only. Crashed programs are crashed, and should not try to do anything that may depend on the program state. That most likely includes formatted output. Ubuntu, Windows and MacOS have dedicated crash reporting tools that work from outside the crashed process and know how to capture all threads and full memory contents. For that to work we'd need to archive debug information and match it against crash reports. Simon
signature.asc
Description: OpenPGP digital signature
_______________________________________________ Mailing list: https://launchpad.net/~kicad-developers Post to : kicad-developers@lists.launchpad.net Unsubscribe : https://launchpad.net/~kicad-developers More help : https://help.launchpad.net/ListHelp
