Thank you for replying.
Even though I've been using Debian since 2010 (and Ubuntu for 5 years
before that), it is the first time I am asked to provide a core dump,
so I might need some help getting there.
I added the dbgsym repos, and installed the following packages
suggested by find-dbgsym-packages:
libacl1-dbgsym libatk-bridge2.0-0t64-dbgsym libatk1.0-0t64-dbgsym
libatomic1-dbgsym libatspi2.0-0t64-dbgsym libbrotli1-dbgsym libbz2-1.0-
dbgsym libcairo-gobject2-dbgsym libcairo2-dbgsym libcanberra0-dbgsym
libcap2-dbgsym libcloudproviders0-dbgsym libcrypt1-dbgsym libdbus-1-3-
dbgsym libepoxy0-dbgsym libexpat1-dbgsym libffi8-dbgsym libfontconfig1-
dbgsym libfreetype6-dbgsym libfribidi0-dbgsym libgdk-pixbuf-2.0-0-
dbgsym libgmp10-dbgsym libgpm2-dbgsym libgraphite2-3-dbgsym libgtk-3-
0t64-dbgsym libharfbuzz0b-dbgsym libice6-dbgsym libjpeg62-turbo-dbgsym
libltdl7-dbgsym liblua5.1-0-dbgsym libogg0-dbgsym libpango-1.0-0-dbgsym
libpangocairo-1.0-0-dbgsym libpangoft2-1.0-0-dbgsym libpcre2-8-0-dbgsym
libpixman-1-0-dbgsym libpng16-16t64-dbgsym libruby3.3-dbgsym
libselinux1-dbgsym libsm6-dbgsym libsodium23-dbgsym libsystemd0-dbgsym
libtcl8.6-dbgsym libtdb1-dbgsym libthai0-dbgsym libtinfo6-dbgsym
libvorbis0a-dbgsym libvorbisfile3-dbgsym libwayland-client0-dbgsym
libwayland-cursor0-dbgsym libwayland-egl1-dbgsym libx11-6-dbgsym
libxau6-dbgsym libxcb-render0-dbgsym libxcb-shm0-dbgsym libxcb1-dbgsym
libxcomposite1-dbgsym libxcursor1-dbgsym libxdamage1-dbgsym libxdmcp6-
dbgsym libxext6-dbgsym libxfixes3-dbgsym libxi6-dbgsym libxinerama1-
dbgsym libxkbcommon0-dbgsym libxrandr2-dbgsym libxrender1-dbgsym
libxt6t64-dbgsym perl-debug python3.13-dbg vim-gtk3-dbgsym zlib1g-
dbgsym
But the following packages couldn't be installed due to dependency
issues: libblkid1-dbgsym libglib2.0-0t64-dbgsym libmount1-dbgsym
libuuid1-dbgsym.
I verified that /usr/lib/sysctl.d/50-coredump.conf has the required
configuration, changed the core ulimit to 100000, rebooted and checked
that systemd-coredump.socket is running.
I launched gvim, and when it crashes, what I get is:
--------------------------------
$ coredumpctl -1 debug
Hint: You are currently not seeing messages from other users and the
system.
Users in groups 'adm', 'systemd-journal' can see all messages.
Pass -q to turn off this notice.
PID: 8398 (gvim)
UID: 1000 (jwm)
GID: 1000 (jwm)
Signal: 11 (SEGV)
Timestamp: Wed 2025-05-21 01:16:52 -05 (23min ago)
Command Line: /usr/bin/gvim -f
Executable: /usr/bin/vim.gtk3
Control Group:
/user.slice/user-1000.slice/user@1000.service/app.slice/app-gnome-gvim-
8398.scope
Unit: user@1000.service
User Unit: app-gnome-gvim-8398.scope
Slice: user-1000.slice
Owner UID: 1000 (jwm)
Boot ID: 33f432653b1d46bfb9a95e033563b0b7
Machine ID: 12d242f2786840fb9da7cf99507f17cc
Hostname: <host>
Storage:
/var/lib/systemd/coredump/core.gvim.1000.33f432653b1d46bfb9a95e033563b0
b7.8398.1747808212000000.zst (truncated)
Size on Disk: 5.1M
Message: Process 8398 (gvim) of user 1000 dumped core.
Module /usr/lib/x86_64-linux-gnu/libgcc_s.so.1 from deb gcc-14-14.2.0-
19.amd64
Stack trace of thread 8398:
#0 0x00007f85e004a007 n/a (n/a + 0x0)
ELF object binary architecture: AMD x86-64
GNU gdb (Debian 16.3-1) 16.3
Copyright (C) 2024 Free Software Foundation, Inc.
License GPLv3+: GNU GPL version 3 or later
<http://gnu.org/licenses/gpl.html>
This is free software: you are free to change and redistribute it.
There is NO WARRANTY, to the extent permitted by law.
Type "show copying" and "show warranty" for details.
This GDB was configured as "x86_64-linux-gnu".
Type "show configuration" for configuration details.
For bug reporting instructions, please see:
<https://www.gnu.org/software/gdb/bugs/>.
Find the GDB manual and other documentation resources online at:
<http://www.gnu.org/software/gdb/documentation/>.
For help, type "help".
Type "apropos word" to search for commands related to "word"...
Reading symbols from /usr/bin/vim.gtk3...
Reading symbols from /usr/lib/debug/.build-
id/8a/a4d2b84c391e9750c5b30840c40af51e364721.debug...
warning: BFD: warning: /var/tmp/coredump-MgBBRz has a segment extending
past end of file
warning: Can't open file /SYSV00000000 (deleted) during file-backed
mapping note processing
[New LWP 8398]
[New LWP 8403]
[New LWP 8408]
[New LWP 8400]
[New LWP 8402]
[New LWP 8401]
warning: failed to parse execution context from corefile: Cannot access
memory at address 0x7ffd376e0fe8
warning: Error reading shared library list entry at 0x7472747368732e00
Failed to read a valid object file image from memory.
Core was generated by `/usr/bin/gvim -f'.
Program terminated with signal SIGSEGV, Segmentation fault.
(ins)--Type <RET> for more, q to quit, c to continue without paging--c
#0 0x00007f85e004a007 in ?? ()
[Current thread is 1 (LWP 8398)]
(ins)(gdb) set pagination off
(ins)(gdb) bt
#0 0x00007f85e004a007 in ?? ()
Backtrace stopped: Cannot access memory at address 0x7ffd376d26d8
(ins)(gdb) bt full
#0 0x00007f85e004a007 in ?? ()
No symbol table info available.
Backtrace stopped: Cannot access memory at address 0x7ffd376d26d8
(ins)(gdb) thread apply all bt full
Thread 6 (LWP 8401):
#0 0x00007f85e00a49ee in ?? ()
No symbol table info available.
#1 0x00007f85e0099668 in ?? ()
No symbol table info available.
#2 0x00007f85de9fe9c8 in ?? ()
No symbol table info available.
#3 0x0000000000000000 in ?? ()
No symbol table info available.
Thread 5 (LWP 8402):
#0 0x00007f85e00a49ee in ?? ()
No symbol table info available.
#1 0x00007f85e0099668 in ?? ()
No symbol table info available.
#2 0x00007f85de1fd9c8 in ?? ()
No symbol table info available.
#3 0x0000000000000000 in ?? ()
No symbol table info available.
Thread 4 (LWP 8400):
#0 0x00007f85e0118779 in ?? ()
No symbol table info available.
Backtrace stopped: Cannot access memory at address 0x7f85df1fe778
Thread 3 (LWP 8408):
#0 0x00007f85e00a49ee in ?? ()
No symbol table info available.
#1 0x00007f85e0099668 in ?? ()
No symbol table info available.
#2 0x00007f85dcf5e088 in ?? ()
No symbol table info available.
#3 0x0000000000000000 in ?? ()
No symbol table info available.
Thread 2 (LWP 8403):
#0 0x00007f85e0118779 in ?? ()
No symbol table info available.
#1 0x00007f85e1a7e0c4 in ?? ()
No symbol table info available.
#2 0x00005575982cb870 in ?? ()
No symbol table info available.
#3 0xffffffffffffffff in ?? ()
No symbol table info available.
#4 0x00005575982cb888 in ?? ()
No symbol table info available.
#5 0x0000000000000001 in ?? ()
No symbol table info available.
#6 0x00005575982cb878 in ?? ()
No symbol table info available.
#7 0x00007f85e1a1477b in ?? ()
No symbol table info available.
#8 0x00005575982cb870 in ?? ()
No symbol table info available.
#9 0x00005575982cb870 in ?? ()
No symbol table info available.
#10 0x00007f85d40097b0 in ?? ()
No symbol table info available.
#11 0x00000862d39e7b17 in ?? ()
No symbol table info available.
#12 0x00007ffd376de760 in ?? ()
No symbol table info available.
#13 0x00007f85e1a14c2b in ?? ()
No symbol table info available.
#14 0x00007f85d40097b0 in ?? ()
No symbol table info available.
#15 0x0000557599444b40 in ?? ()
No symbol table info available.
#16 0x00005575982cb870 in ?? ()
No symbol table info available.
#17 0x00007f85e16022a7 in ?? ()
No symbol table info available.
#18 0x0000000000000000 in ?? ()
No symbol table info available.
Thread 1 (LWP 8398):
#0 0x00007f85e004a007 in ?? ()
No symbol table info available.
Backtrace stopped: Cannot access memory at address 0x7ffd376d26d8
--------------------------------
Since last year, I've been unable to use gdb properly. Both the version
installed through APT and the one that comes with Intel oneAPI throw
the same internal error (due to this
bug: https://sourceware.org/bugzilla/show_bug.cgi?id=32793), so I don't
know whether the results above are a consequence of that bug or if I'm
missing some step.
The core file is attached.