http://bugs.winehq.org/show_bug.cgi?id=58742
--- Comment #3 from Eric Pouech eric.pouech@gmail.com --- can you get debug info from your build now?
wow or CFLAGS shouldn't play a role here
the crash can only happen for an image file that has debug-stripped bit set and no debug directory present
'''winedump -f <img>''' should show DEBUG STRIPPED '''winedump -j debug <img>''' should show no information
but this could come from any loaded module in debugger (either main image, or any of the DLL)
if this happened for every app, it's likely that one of wine modules (potentially ntdll or kernelbase, for which winedbg always load debug info at startup) triggered the crash
cause outside of compilation/configuration options could come also from a truncated image file (out of disk space, or other causes...)
and a fresh compilation makes it vanish