5 Commits

Author	SHA1	Message	Date
Linus Groh	45f00ce38d	CrashReporter: Show assertion message in backtrace, if any	2020-12-30 16:28:27 +01:00
Linus Groh	761169f5c0	CrashReporter: Show PID from coredump	2020-12-30 15:00:17 +01:00
Linus Groh	bde65ba7ca	CrashReporter: Read executable path from coredump process info ... We no longer have to look at the backtrace and guess the executable, it's now embedded in the coredump's ProcessInfo notes entry directly. Fixes #4645.	2020-12-30 15:00:17 +01:00
Andreas Kling	10b5b9ee66	CrashReporter: Don't keep the coredump file open longer than necessary ... Let's be nice and close the file after we've extracted what we need.	2020-12-30 02:56:31 +01:00
Linus Groh	b13b27b4d2	Applications: Add CrashReporter :^) ... This is a simple application that can read a coredump file and display information regarding the crash, like the application's name and icon and a backtrace. It will be launched by CrashDaemon whenever a new coredump is available. Also, it's mostly written in GML! :^) Closes #400, but note that, unlike mentioned in that issue, this implementation doesn't ignore applications that "have been started in the terminal". That's just overcomplicating things, IMO. When my js(1) REPL segfaults, I want to see a backtrace!	2020-12-29 15:42:30 +01:00