Apport doesn't log when a core dump is ignored because of the limit
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
apport (Ubuntu) |
Confirmed
|
Wishlist
|
Unassigned |
Bug Description
When ulimit -c is 0, apport doesn't report any reason not to skip the dumping. For applications that are not packaged, the last message in /var/log/apport.log is:
ERROR: apport (pid 4415) Mon Nov 25 17:52:11 2013: executable does not belong to a package, ignoring
This makes very confusing diagnosing why the core was not generated, and is very hard to track down how the particular ulimit of the application was configured, so it would be better to add a message telling the core dump won't be generated because the limit is 0.
Basically the suggested change is:
if limit == '0':
+ error_log('skipping core dump writing, current limit is 0')
return
ProblemType: Bug
DistroRelease: Ubuntu 12.04
Package: apport 2.0.1-0ubuntu17.6 [modified: usr/share/
ProcVersionSign
Uname: Linux 3.5.0-41-generic x86_64
ApportVersion: 2.0.1-0ubuntu17.6
Architecture: amd64
CrashReports:
664:1000:
640:1000:
600:122:
Date: Mon Nov 25 18:16:02 2013
MarkForUpload: True
PackageArchitec
SourcePackage: apport
UpgradeStatus: Upgraded to precise on 2012-05-24 (550 days ago)
Changed in apport (Ubuntu): | |
importance: | Undecided → Wishlist |
summary: |
- [wishlist] Apport doesn't log when a core dump is ignored because of the - limit + Apport doesn't log when a core dump is ignored because of the limit |
That would be nice to have built in. Any application that generates it's own crash report should state why a core dump wasn't created, but it isn't part of apport functionality to report why a core wasn't generated.