Allowing cores for packaged programs if ulimit permits is sufficient for our needs.
We actually adjust ulimit early in the process because we want customers to optionally submit cores for debugging. (Glad to hear VMware software doesn't dump core for you ;-) - I wish our betas were that robust!). >The primary reason is that SIGABRT is mainly used on assertion failures in C and Mono. Sounds like a package-specific suppression override later in the process - like 87430. Fine that they don't want cores - but it becomes problematic if that blocks our cores. Thanks for the Mono link - I'm learning interesting new ways to hook apport! And many thanks for the quick communication! -- 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
