GNOME Bugzilla – Bug 692032
build: Add --disable-segv-handler option
Last modified: 2013-01-22 17:50:56 UTC
Modern operating systems come with systemwide "crash catching" facilities; for example, the Linux kernel can now pipe core dumps out to userspace, and programs like "systemd-coredump" and "abrt" record these. In this model, it's actively counterproductive for individual processes to catch SIGSEGV because: 1) Trying to unwind from inside the process after arbitrary corruption is destined to fail. 2) It hides the fact that a crash happened at all - my OS test framework wants to know if any process crashed, and I don't want to guess by running regexps against /var/log/Xorg.0.log or whatever.
Created attachment 233791 [details] [review] 0001-build-Add-disable-segv-handler-option.patch
i'm not sure there's really any reason to make it configurable...
(In reply to comment #2) > i'm not sure there's really any reason to make it configurable... I'm happy to prep a patch to delete it - even RHEL6 had abrt backported in 6.1, so there really aren't any relevant operating systems to which current NM git might possibly run that don't have crash catching in userspace.
Created attachment 233865 [details] [review] 0001-Remove-SIGSEGV-SIGFPE-etc.-handling.patch
See also: http://lists.x.org/archives/xorg-devel/2013-January/035185.html https://bugzilla.gnome.org/show_bug.cgi?id=676181
Yes kill it.
Review of attachment 233865 [details] [review]: Good
pushed