https://gcc.gnu.org/bugzilla/show_bug.cgi?id=105700
Alexander Monakov <amonakov at gcc dot gnu.org> changed:
What |Removed |Added
----------------------------------------------------------------------------
CC| |amonakov at gcc dot gnu.org
--- Comment #3 from Alexander Monakov <amonakov at gcc dot gnu.org> ---
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?
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.
