Thanks for the quick reply. I'm not talking about any "crash report", I'm talking about development, when trying locally something that you just compiled. Also, is apport the one deciding not to generate the core (of course when the limit is 0 that is expected and correct behaviour, but nothing the application can, or should deal with).
Also, even when maybe is not part of apport functionality to report why a core wasn't generated, it is already doing it, as is obviously extremely convenient for diagnosing, and because of how these diagnose messages are generated, it makes very hard to diagnose the ulimit problem (as it looks like the core dump wasn't generated because it's not a packaged app). I even was about to report a bug about apport not generating cores for 3rd party programs because of this, but fortunately I went through the source code and found the limit could be the reason (and it was). Finally, is a one line change, is a completely unintrusive change and in line with the other diagnose messages generated, and it makes a huge difference when trying to debug something you are developing, so it would be very appreciated if you could add this small change. Thanks! -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1254804 Title: [wishlist] Apport doesn't log when a core dump is ignored because of the limit To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/apport/+bug/1254804/+subscriptions -- ubuntu-bugs mailing list [email protected] https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
