Suggestion: Configure apport (?) to write coredumps for custom applications in working directory

Bug #1850161 reported by DarkTrick
8
This bug affects 1 person
Affects Status Importance Assigned to Milestone
apport (Ubuntu)
New
Undecided
Unassigned

Bug Description

- Regarding XUbuntu 19.04
- apport version: 2.20.10-0ubuntu27.1

Current behaviour:
==================
Core dumps of custom software (e.g. self-created software) are not created by default.
(It says "core dumped", but actually nothing was created. This is a bug, but not of matter now)

To create coredumps within `/var/crash/`, one has to
- Create `~/.config/apport/settings` with the following content:

    [main]
    unpackaged=true

- set ulimit -c unlimited

Suggested behaviour:
====================
Setup apport (? or whatever package is in charge) to
- create core dumps of custom software
- inside the current working directory
- by default

Alternative Suggested behaviour:
====================
Setup apport (? or whatever package is in charge) to
- create core dumps of custom software
- inside the current working directory
- after setting `ulimit -c unlimited`

Revision history for this message
DarkTrick (darktrick1337) wrote :

edit @ Current behaviour:
Core dumps are not created in `/var/crash`. Crash files are created there. They must be further processed to gain the real coredump.

Revision history for this message
Theo Linkspfeifer (lastonestanding) wrote :

Any reason why this change (if it makes sense) should be specific to Xubuntu?

Revision history for this message
DarkTrick (darktrick1337) wrote :

If the behaviour on ubuntu is the same, it's not specific to Xubuntu.

affects: xubuntu-default-settings (Ubuntu) → apport (Ubuntu)
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.