Hi, Todays Apport (2.0.1) filters core dump on SIGQUIT. I'm not sure it is a good choice. The excuse put forward is that "SIGQUIT is usually deliberately generated by users". And then?
Sure, SIGQUIT is deliberately generated by users. Users may deliberately do want a core-dump of a process. They may have a number of very good reasons for this. Whatever the reasons, this behavior (core dump on SIGQUIT) is normalized since POSIX.1-1990 (see man signal(7)). Users can expect Ubuntu to follow the standards. If you believe that this standard is inadequate, you can discuss this point in IEEE working groups. In the meantime, you should be well aware that Apport violates POSIX standrads. So, can I suggest you reconsider your choice (and let Apport generate core dump on SIGQUIT)? Otherwise, may I suggest you to clearly document your choice to prevent users of this non-standard behavior? In addition, it would be good to provide a means for users to configure the behavior of Apport with respect to their process (via an environment variable, a configuration file in their home directory, etc.) Best regards Christophe -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/62511 Title: dumps core on SIGQUIT To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/apport/+bug/62511/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
