https://gcc.gnu.org/bugzilla/show_bug.cgi?id=105700
--- Comment #4 from Artem S. Tashkinov <aros at gmx dot com> --- (In reply to Alexander Monakov from comment #3) > It seems you're already getting some good advice on the Wine Bugzilla > (thanks for linking it in the URL field). > > 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 > > Hopefully with the help of Wine folks you'll manage to attach GDB properly > to observe the crash, but one other thing you could do is bisect the > miscompiled binary: if you have two Wine installations, one broken (with > -march=pentium-m) and one working fine (without the flag), then you can take > half of binaries from one and half from another and see if it still crashes. > Depending on the outcome you know which half contains a broken binary. > Continuing this process, you can narrow it down to one file. That's a good but quite herculean in terms of effort idea. If nothing else works, I will try it.
