https://bugs.winehq.org/show_bug.cgi?id=56829
--- Comment #8 from mushu csumushu@126.com --- (In reply to Eric Pouech from comment #6)
I’m very sorry, but due to company network restrictions, I cannot upload the log file. Are there any keywords I can look for?
there are three different things you could try:
- rerun the program with
WINEDEBUG=+dbghelp,+dbghelp_symt,+dbghelp_dwarf,+dbghelp_msc,+seh in the generated log file, find out either:
- there should be traces about launching winedbg or triggering
- locate the exception (seh) before that and share the location of the crash
- locate the dbghelp SymLoadModule* trace before that and share that
information 2) in the window that pops named winedbg, can you actually copy the backtrace that appears? (you can limit that to the frames corresponding to wine components) 3) are there in the application directory (and/or its subdirectories) named *.pdb? if so, it would be interesting to rerun the program without these files (ie move them outside of the app dir - of course remembering where they were and put them back in place afterwards)
Method 3 can solve the problem. Why is that so?