https://gcc.gnu.org/bugzilla/show_bug.cgi?id=105700
--- Comment #5 from Alexander Monakov <amonakov at gcc dot gnu.org> --- (In reply to Artem S. Tashkinov from comment #4) > > There should be a note in dmesg when a process segfaults outside of a > > debugger. If you run wine without gdb, and winedevice.exe crashes, is there > > a corresponding message in dmesg? > > Just this: > > [????] Process 577885 (winedevice.exe) of user 1000 dumped core. > Stack trace of thread 577888: > #0 0x00000000f7d51e7d n/a (n/a + 0x0) > #1 0x00000000f7d528f7 n/a (n/a + 0x0) > ELF object binary architecture: Intel 80386 This is what systemd-coredump prints. Are you sure the kernel is not printing a notification in dmesg? It may include useful information such as register state and binary code around the failing instruction. On my system it looks like this: a.out[13922]: segfault at 0 ip 0000000008049000 sp 00000000ffdc8520 error 4 in a.out[8048000+2000] Code: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 <a1> 00 00 00 00 0f 0b 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 m > That's a good but quite herculean in terms of effort idea. If nothing else > works, I will try it. Each step reduces number of suspicious binaries by half, so only 7 steps for 128 binaries.
