Running make test_3 doesn't produce a core dump. This applies to commit 07bfd96.
To find where core dumps are being routed, I ran the following command:
cat /proc/sys/kernel/core_pattern
returns
|/usr/share/apport/apport -p%p -s%s -c%c -d%d -P%P -u%u -g%g -F%F -- %E
This means Ubuntu is using Apport to manage core dumps. I checked the liveness of Apport using the following command:
returns:
● apport.service - automatic crash report generation
Loaded: loaded (/usr/lib/systemd/system/apport.service; enabled; preset: enabled)
Active: active (exited) since Sun 2026-06-21 19:21:34 AEST; 5h 8min ago
Main PID: 1450 (code=exited, status=0/SUCCESS)
CPU: 495ms
Jun 21 19:21:17 coogee systemd[1]: Starting apport.service - automatic crash report generation...
Jun 21 19:21:34 coogee systemd[1]: Finished apport.service - automatic crash report generation.
Normally, Apport writes core dumps as .crash files in /var/crash directory. I checked for existing core dumps:
returns only two (2) core dumps, neither at the time the program ran:
-rw-r----- 1 douglas whoopsie 32338540 Jun 14 19:24 /var/crash/_usr_bin_gnome-shell.1000.crash
-rw-r----- 1 gdm whoopsie 26489450 Jun 14 19:23 /var/crash/_usr_bin_gnome-shell.121.crash
Running
make test_3doesn't produce a core dump. This applies to commit 07bfd96.To find where core dumps are being routed, I ran the following command:
returns
This means Ubuntu is using Apport to manage core dumps. I checked the liveness of Apport using the following command:
returns:
Normally, Apport writes core dumps as
.crashfiles in/var/crashdirectory. I checked for existing core dumps:ls -l /var/crash/*.crashreturns only two (2) core dumps, neither at the time the program ran: