Comment 0 for bug 1982555

Revision history for this message
Benjamin Drung (bdrung) wrote :

[Impact]

Apport will write an empty core dump file inside of containers.

[Test plan]

Run following testcase script inside a LXC container:

```
rm -f /var/lib/apport/coredump/*
ulimit -c 1000000
sleep 86400 &
killall -3 sleep
```

Apport will write a core dump into /var/lib/apport/coredump, but this core dump is empty:

```
$ stat /var/lib/apport/coredump/core._usr_bin_sleep.*
  File: /var/lib/apport/coredump/core._usr_bin_sleep.0.44f483a1-e487-44b3-88d1-805d1026f31d.9059.34839819
  Size: 0 Blocks: 0 IO Block: 4096 regular empty file
Device: fd00h/64768d Inode: 120848663 Links: 1
Access: (0400/-r--------) Uid: ( 0/ root) Gid: ( 0/ root)
Access: 2022-07-22 07:54:48.838682067 +0000
Modify: 2022-07-22 07:54:48.838682067 +0000
Change: 2022-07-22 07:54:48.838682067 +0000
 Birth: 2022-07-22 07:54:48.838682067 +0000
```

This file should not be empty.

[Other Info]

The autopkgtest for armhf are run inside a LXC container and the test case test_core_dump_packaged_sigquit triggers this bug.