On Fri, 2013-01-18 at 14:19 -0500, Colin Walters wrote: > 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. > > Signed-off-by: Colin Walters <[email protected]>
Reviewed-by: Adam Jackson <[email protected]> - ajax _______________________________________________ [email protected]: X.Org development Archives: http://lists.x.org/archives/xorg-devel Info: http://lists.x.org/mailman/listinfo/xorg-devel
