> Will your patch also allow SIGABRT-generated reports to reach (2)? Not according to my initial intentions, due to the principle of /proc/sys/kernel/core_pattern. (Also, VMWare works fine for me without throwing core dumps around, FWIW).
However, thinking about it again apport *could* write core dumps for packaged programs as well if ulimits permit. Since we default to ulimit -c 0, this would not change the default behaviour, and it would make the behaviour more consistent as well. > Is there a reason to drop SIGABRT reports even from packaged installations? Should such a reason be package-specific? (Or is more work in progress? :-) ) The primary reason is that SIGABRT is mainly used on assertion failures in C and Mono. Since we currently do not have a possibility to get the assertion message, crash reports are useless. Our Gnome and Mono maintainers thus asked me to ignore ABRT in apport. There are, however, ideas how to get assertion messages, and there is a spec for Mono (https://wiki.ubuntu.com/ApportMonoCrashes). -- Generate core dumps for packaged programs as well https://launchpad.net/bugs/92029 -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
