[Bug 56829] New: Program Crashes Unexpectedly After Updating Wine Version from WineHQ Repository
https://bugs.winehq.org/show_bug.cgi?id=56829 Bug ID: 56829 Summary: Program Crashes Unexpectedly After Updating Wine Version from WineHQ Repository Product: Wine Version: 8.0.1 Hardware: x86-64 OS: Linux Status: UNCONFIRMED Severity: normal Priority: P2 Component: -unknown Assignee: wine-bugs(a)winehq.org Reporter: csumushu(a)126.com Distribution: --- “When I installed Wine 8.0 from the Ubuntu software source on Ubuntu 23.10, the program worked fine. However, after switching to WineHQ’s repository and updating to Wine 9.0 on Ubuntu 23.10, the same program crashed due to an assert error when running with Wine. Interestingly, installing Wine 9.0 from the Ubuntu software source on Ubuntu 24.04 works without any issues. What could be the reason for this?” The following is the error when running in the Wine 9.0 environment on Ubuntu 23.10. root(a)mushu:~/osn8800# WINEDEBUG=fixme-all wine64 winosp_release/winospexe/winosp.exe "C:\\ProgramData\\ne1\\WINOSPHARDCFG.INI" 02a0:err:msvcrt:_wassert (L"!sig_type || sig_type->tag == SymTagFunctionType",L"dlls/dbghelp/symbol.c",329) -- Do not reply to this email, post in Bugzilla using the above URL to reply. You are receiving this mail because: You are watching all bug changes.
https://bugs.winehq.org/show_bug.cgi?id=56829 mushu <csumushu(a)126.com> changed: What |Removed |Added ---------------------------------------------------------------------------- Version|8.0.1 |9.0 -- Do not reply to this email, post in Bugzilla using the above URL to reply. You are receiving this mail because: You are watching all bug changes.
https://bugs.winehq.org/show_bug.cgi?id=56829 --- Comment #1 from mushu <csumushu(a)126.com> --- Installing Wine from the WineHQ repository shows the version as 9.0 when using the wine --version command, while installing Wine from the Ubuntu repository shows the version as 9.0~repack-4build3 with the same command. What is the difference between them? -- Do not reply to this email, post in Bugzilla using the above URL to reply. You are receiving this mail because: You are watching all bug changes.
https://bugs.winehq.org/show_bug.cgi?id=56829 --- Comment #2 from mushu <csumushu(a)126.com> --- Created attachment 76637 --> https://bugs.winehq.org/attachment.cgi?id=76637 log file -- Do not reply to this email, post in Bugzilla using the above URL to reply. You are receiving this mail because: You are watching all bug changes.
https://bugs.winehq.org/show_bug.cgi?id=56829 Eric Pouech <eric.pouech(a)gmail.com> changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |eric.pouech(a)gmail.com --- Comment #3 from Eric Pouech <eric.pouech(a)gmail.com> --- Two questions: - is the winosp program freely available somewhere? - can you attach the output of running with WINEDEBUG=+dbghelp_symt (compressed, could be huge) TIA -- Do not reply to this email, post in Bugzilla using the above URL to reply. You are receiving this mail because: You are watching all bug changes.
https://bugs.winehq.org/show_bug.cgi?id=56829 --- Comment #4 from mushu <csumushu(a)126.com> --- the `winosp` program is not freely available online. the log file is attached. There is a strange issue. If I run the program with WINEDEBUG=fixme-all,+dbghelp_symt or WINEDEBUG=dbghelp_symt, the program exits quickly. I can’t find the assertion in the logs, and two windows pop up: one titled ‘wine debugger’ and the other ‘program error.’ However, if I run the program with WINEDEBUG=fixme-all, only the assertion log appears. -- Do not reply to this email, post in Bugzilla using the above URL to reply. You are receiving this mail because: You are watching all bug changes.
https://bugs.winehq.org/show_bug.cgi?id=56829 --- Comment #5 from mushu <csumushu(a)126.com> --- (In reply to Eric Pouech from comment #3)
Two questions: - is the winosp program freely available somewhere? - can you attach the output of running with WINEDEBUG=+dbghelp_symt (compressed, could be huge)
TIA
I’m very sorry, but due to company network restrictions, I cannot upload the log file. Are there any keywords I can look for? -- Do not reply to this email, post in Bugzilla using the above URL to reply. You are receiving this mail because: You are watching all bug changes.
https://bugs.winehq.org/show_bug.cgi?id=56829 --- Comment #6 from Eric Pouech <eric.pouech(a)gmail.com> ---
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: 1) 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) -- Do not reply to this email, post in Bugzilla using the above URL to reply. You are receiving this mail because: You are watching all bug changes.
https://bugs.winehq.org/show_bug.cgi?id=56829 --- Comment #7 from Eric Pouech <eric.pouech(a)gmail.com> --- crash is similar as the one reported in [1] hard to tell without more info if the cause is the same [1] https://bugs.winehq.org/show_bug.cgi?id=56577 -- Do not reply to this email, post in Bugzilla using the above URL to reply. You are receiving this mail because: You are watching all bug changes.
https://bugs.winehq.org/show_bug.cgi?id=56829 --- Comment #8 from mushu <csumushu(a)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: 1) 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? -- Do not reply to this email, post in Bugzilla using the above URL to reply. You are receiving this mail because: You are watching all bug changes.
https://bugs.winehq.org/show_bug.cgi?id=56829 --- Comment #9 from Eric Pouech <eric.pouech(a)gmail.com> ---
Method 3 can solve the problem. Why is that so? these .pdb files contain symbolic debug information, which are loaded by dbghelp likely something goes wrong it this process
-- Do not reply to this email, post in Bugzilla using the above URL to reply. You are receiving this mail because: You are watching all bug changes.
https://bugs.winehq.org/show_bug.cgi?id=56829 --- Comment #10 from mushu <csumushu(a)126.com> --- here is the rerun log: ------------------------------- 079c:trace:dbghelp:SymLoadModuleExW (FFFFFFFF 00000000 L"Z:\\usr1\\winosp_release\\winospexe\\winosp.exe" (null) 400000 0c7ae000 00000000 00000000) ----------------------------- 079c:fixme:dbghelp_msc:codeview_get_type Returning NULL symt for type-id 11fe 079c:fixme:dbghelp_msc:pdb_global_feed_types S-Udt "tagDHCP4RShellCallbackSet": couldn't find type 0x11fe 079c:fixme:dbghelp_msc:codeview_get_type Returning NULL symt for type-id 10a4 079c:fixme:dbghelp_msc:pdb_global_feed_types S-Udt "_CMSCBB_CALLBACK_FUNCS": couldn't find type 0x10a4 079c:fixme:dbghelp_msc:codeview_get_type Returning NULL symt for type-id 113c1 079c:fixme:dbghelp_msc:pdb_global_feed_types S-Udt "cmscbb_ctx_create_params_st": couldn't find type 0x113c1 079c:fixme:dbghelp_msc:codeview_get_type Returning NULL symt for type-id 11457 079c:fixme:dbghelp_msc:pdb_global_feed_types S-Udt "cmscbb_sys_plantform_funcs_st": couldn't find type 0x11457 079c:trace:dbghelp_symt:symt_new_compiland Adding compiland symbol L"winosp":"* CIL *" 079c:trace:dbghelp_msc:codeview_snarf S-ObjName-V3 "* CIL *" 079c:trace:dbghelp_msc:codeview_snarf S-Compile3-V3 machine:3 language:7 "Microsoft (R) LINK" 079c:trace:dbghelp_msc:codeview_snarf_linetab2 No DEBUG_S_FILECHKSMS found 079c:trace:dbghelp_symt:symt_new_compiland Adding compiland symbol L"winosp":"Release\\v_configkernel.obj" 079c:trace:dbghelp_msc:codeview_snarf S-ObjName-V3 "M:\\DOPRASSPV300R002C20SPC013B020V1Adapt\\target\\project\\win32\\demo\\demo\\Release\\v_configkernel.obj" 079c:trace:dbghelp_msc:codeview_snarf S-Compile3-V3 machine:7 language:0 "Microsoft (R) Optimizing Compiler" 079c:trace:dbghelp_symt:symt_new_function Adding global function L"winosp":"CFG_RegisterBasicKernelInfo" @4013d0-4013d2 079c:trace:dbghelp_symt:symt_new_function Adding global function L"winosp":"VOS_McAndHwMsgInit" @4013c0-4013c2 079c:err:msvcrt:_wassert (L"!sig_type || sig_type->tag == SymTagFunctionType",L"dlls/dbghelp/symbol.c",329) Assertion failed: !sig_type || sig_type->tag == SymTagFunctionType, file dlls/dbghelp/symbol.c, line 329^M ^M 079c:trace:seh:raise (22) 079c:warn:seh:dispatch_exception "BCGCBPRO.DLL Terminating!\n" 079c:trace:seh:dispatch_exception code=40010006 (DBG_PRINTEXCEPTION_C) flags=0 addr=7B64A527 079c:trace:seh:dispatch_exception info[0]=0000001B 079c:trace:seh:dispatch_exception info[1]=0EDA8FC8 079c:trace:seh:dispatch_exception eip=7b64a527 esp=0eda6d44 ebp=0eda6d98 eflags=00000246 079c:trace:seh:dispatch_exception eax=0eda6d44 ebx=0000001b ecx=00000004 edx=0eda6dd4 079c:trace:seh:dispatch_exception esi=0edac800 edi=0edac570 cs=0023 ds=002b es=002b fs=0063 gs=006b ss=002b 079c:trace:seh:call_seh_handlers calling handler at 7BBA6690 code=40010006 flags=0 079c:trace:seh:__regs_RtlUnwind code=40010006 flags=2 079c:trace:seh:__regs_RtlUnwind eip=7bb8ef1e esp=0eda5a58 ebp=0eda5a60 eflags=00000212 079c:trace:seh:__regs_RtlUnwind eax=00000000 ebx=00000000 ecx=40010006 edx=0eda6ddc 079c:trace:seh:__regs_RtlUnwind esi=0eda5b88 edi=0eda5b88 cs=0023 ds=002b es=002b fs=0063 gs=006b ss=002b 079c:trace:seh:__regs_RtlUnwind calling handler at 7BD5E1A0 code=40010006 flags=2 079c:trace:seh:__regs_RtlUnwind handler at 7BD5E1A0 returned 1 079c:trace:seh:dispatch_exception code=80000003 (EXCEPTION_BREAKPOINT) flags=0 addr=797C5D88 079c:trace:seh:dispatch_exception info[0]=00000000 079c:trace:seh:dispatch_exception eip=797c5d88 esp=0edac5c0 ebp=0edac5d8 eflags=00000202 079c:trace:seh:dispatch_exception eax=00000001 ebx=003534a0 ecx=5d3885c0 edx=79bb04d8 079c:trace:seh:dispatch_exception esi=0edac800 edi=003534a0 cs=0023 ds=002b es=002b fs=0063 gs=006b ss=002b 079c:trace:seh:call_seh_handlers calling handler at 79831DE9 code=80000003 flags=0 079c:trace:seh:call_seh_handlers handler at 79831DE9 returned 1 079c:trace:seh:call_seh_handlers calling handler at 798523DA code=80000003 flags=0 079c:trace:seh:call_seh_handlers handler at 798523DA returned 1 079c:trace:seh:call_seh_handlers calling handler at 79814720 code=80000003 flags=0 079c:trace:seh:call_seh_handlers handler at 79814720 returned 1 079c:trace:seh:call_seh_handlers calling handler at 7BD398F0 code=80000003 flags=0 079c:trace:seh:__regs_RtlUnwind code=80000003 flags=2 079c:trace:seh:__regs_RtlUnwind eip=7bd0cf6a esp=0edab96c ebp=0edab974 eflags=00000216 079c:trace:seh:__regs_RtlUnwind eax=00000000 ebx=0edac848 ecx=80000003 edx=0edac848 079c:trace:seh:__regs_RtlUnwind esi=7ffb2000 edi=0edaba88 cs=0023 ds=002b es=002b fs=0063 gs=006b ss=002b 079c:trace:seh:__regs_RtlUnwind calling handler at 7BD5E1A0 code=80000003 flags=2 079c:trace:seh:__regs_RtlUnwind handler at 7BD5E1A0 returned 1 079c:trace:seh:__regs_RtlUnwind calling handler at 79831DE9 code=80000003 flags=2 079c:trace:seh:__regs_RtlUnwind handler at 79831DE9 returned 1 079c:trace:seh:__regs_RtlUnwind calling handler at 798523DA code=80000003 flags=2 079c:trace:seh:__regs_RtlUnwind handler at 798523DA returned 1 079c:trace:seh:__regs_RtlUnwind calling handler at 79814720 code=80000003 flags=2 079c:trace:seh:__regs_RtlUnwind handler at 79814720 returned 1 079c:trace:seh:dispatch_exception code=c0000005 (EXCEPTION_ACCESS_VIOLATION) flags=0 addr=03E7C976 079c:trace:seh:dispatch_exception info[0]=00000000 079c:trace:seh:dispatch_exception info[1]=00000048 079c:trace:seh:dispatch_exception eip=03e7c976 esp=0edac1bc ebp=0edac294 eflags=00010212 079c:trace:seh:dispatch_exception eax=00000000 ebx=003533e0 ecx=00000000 edx=0e60d194 079c:trace:seh:dispatch_exception esi=0edac800 edi=0edac294 cs=0023 ds=002b es=002b fs=0063 gs=006b ss=002b 079c:trace:seh:call_seh_handlers calling handler at 07898521 code=c0000005 flags=0 079c:trace:seh:call_seh_handlers handler at 07898521 returned 1 079c:trace:seh:call_seh_handlers calling handler at 79B69550 code=c0000005 flags=0 079c:trace:seh:call_seh_handlers handler at 79B69550 returned 1 079c:trace:seh:call_seh_handlers calling handler at 79B69550 code=c0000005 flags=0 079c:trace:seh:call_seh_handlers handler at 79B69550 returned 1 079c:trace:seh:call_seh_handlers calling handler at 7BD398F0 code=c0000005 flags=0 079c:trace:seh:__regs_RtlUnwind code=c0000005 flags=2 079c:trace:seh:__regs_RtlUnwind eip=7bd0cf6a esp=0edab52c ebp=0edab534 eflags=00000212 079c:trace:seh:__regs_RtlUnwind eax=00000000 ebx=0edac848 ecx=c0000005 edx=0edac848 079c:trace:seh:__regs_RtlUnwind esi=7ffb2000 edi=0edab648 cs=0023 ds=002b es=002b fs=0063 gs=006b ss=002b 079c:trace:seh:__regs_RtlUnwind calling handler at 7BD5E1A0 code=c0000005 flags=2 079c:trace:seh:__regs_RtlUnwind handler at 7BD5E1A0 returned 1 079c:trace:seh:__regs_RtlUnwind calling handler at 07898521 code=c0000005 flags=2 079c:trace:seh:__regs_RtlUnwind handler at 07898521 returned 1 079c:trace:seh:__regs_RtlUnwind calling handler at 79B69550 code=c0000005 flags=2 079c:trace:seh:__regs_RtlUnwind handler at 79B69550 returned 1 079c:trace:seh:__regs_RtlUnwind calling handler at 79B69550 code=c0000005 flags=2 079c:trace:seh:__regs_RtlUnwind handler at 79B69550 returned 1 -- Do not reply to this email, post in Bugzilla using the above URL to reply. You are receiving this mail because: You are watching all bug changes.
https://bugs.winehq.org/show_bug.cgi?id=56829 --- Comment #11 from mushu <csumushu(a)126.com> --- (In reply to Eric Pouech from comment #9)
Method 3 can solve the problem. Why is that so? these .pdb files contain symbolic debug information, which are loaded by dbghelp likely something goes wrong it this process
here is the rerun log: ------------------------------- 079c:trace:dbghelp:SymLoadModuleExW (FFFFFFFF 00000000 L"Z:\\usr1\\winosp_release\\winospexe\\winosp.exe" (null) 400000 0c7ae000 00000000 00000000) ----------------------------- 079c:fixme:dbghelp_msc:codeview_get_type Returning NULL symt for type-id 11fe 079c:fixme:dbghelp_msc:pdb_global_feed_types S-Udt "tagDHCP4RShellCallbackSet": couldn't find type 0x11fe 079c:fixme:dbghelp_msc:codeview_get_type Returning NULL symt for type-id 10a4 079c:fixme:dbghelp_msc:pdb_global_feed_types S-Udt "_CMSCBB_CALLBACK_FUNCS": couldn't find type 0x10a4 079c:fixme:dbghelp_msc:codeview_get_type Returning NULL symt for type-id 113c1 079c:fixme:dbghelp_msc:pdb_global_feed_types S-Udt "cmscbb_ctx_create_params_st": couldn't find type 0x113c1 079c:fixme:dbghelp_msc:codeview_get_type Returning NULL symt for type-id 11457 079c:fixme:dbghelp_msc:pdb_global_feed_types S-Udt "cmscbb_sys_plantform_funcs_st": couldn't find type 0x11457 079c:trace:dbghelp_symt:symt_new_compiland Adding compiland symbol L"winosp":"* CIL *" 079c:trace:dbghelp_msc:codeview_snarf S-ObjName-V3 "* CIL *" 079c:trace:dbghelp_msc:codeview_snarf S-Compile3-V3 machine:3 language:7 "Microsoft (R) LINK" 079c:trace:dbghelp_msc:codeview_snarf_linetab2 No DEBUG_S_FILECHKSMS found 079c:trace:dbghelp_symt:symt_new_compiland Adding compiland symbol L"winosp":"Release\\v_configkernel.obj" 079c:trace:dbghelp_msc:codeview_snarf S-ObjName-V3 "M:\\DOPRASSPV300R002C20SPC013B020V1Adapt\\target\\project\\win32\\demo\\demo\\Release\\v_configkernel.obj" 079c:trace:dbghelp_msc:codeview_snarf S-Compile3-V3 machine:7 language:0 "Microsoft (R) Optimizing Compiler" 079c:trace:dbghelp_symt:symt_new_function Adding global function L"winosp":"CFG_RegisterBasicKernelInfo" @4013d0-4013d2 079c:trace:dbghelp_symt:symt_new_function Adding global function L"winosp":"VOS_McAndHwMsgInit" @4013c0-4013c2 079c:err:msvcrt:_wassert (L"!sig_type || sig_type->tag == SymTagFunctionType",L"dlls/dbghelp/symbol.c",329) Assertion failed: !sig_type || sig_type->tag == SymTagFunctionType, file dlls/dbghelp/symbol.c, line 329^M ^M 079c:trace:seh:raise (22) 079c:warn:seh:dispatch_exception "BCGCBPRO.DLL Terminating!\n" 079c:trace:seh:dispatch_exception code=40010006 (DBG_PRINTEXCEPTION_C) flags=0 addr=7B64A527 079c:trace:seh:dispatch_exception info[0]=0000001B 079c:trace:seh:dispatch_exception info[1]=0EDA8FC8 079c:trace:seh:dispatch_exception eip=7b64a527 esp=0eda6d44 ebp=0eda6d98 eflags=00000246 079c:trace:seh:dispatch_exception eax=0eda6d44 ebx=0000001b ecx=00000004 edx=0eda6dd4 079c:trace:seh:dispatch_exception esi=0edac800 edi=0edac570 cs=0023 ds=002b es=002b fs=0063 gs=006b ss=002b 079c:trace:seh:call_seh_handlers calling handler at 7BBA6690 code=40010006 flags=0 079c:trace:seh:__regs_RtlUnwind code=40010006 flags=2 079c:trace:seh:__regs_RtlUnwind eip=7bb8ef1e esp=0eda5a58 ebp=0eda5a60 eflags=00000212 079c:trace:seh:__regs_RtlUnwind eax=00000000 ebx=00000000 ecx=40010006 edx=0eda6ddc 079c:trace:seh:__regs_RtlUnwind esi=0eda5b88 edi=0eda5b88 cs=0023 ds=002b es=002b fs=0063 gs=006b ss=002b 079c:trace:seh:__regs_RtlUnwind calling handler at 7BD5E1A0 code=40010006 flags=2 079c:trace:seh:__regs_RtlUnwind handler at 7BD5E1A0 returned 1 079c:trace:seh:dispatch_exception code=80000003 (EXCEPTION_BREAKPOINT) flags=0 addr=797C5D88 079c:trace:seh:dispatch_exception info[0]=00000000 079c:trace:seh:dispatch_exception eip=797c5d88 esp=0edac5c0 ebp=0edac5d8 eflags=00000202 079c:trace:seh:dispatch_exception eax=00000001 ebx=003534a0 ecx=5d3885c0 edx=79bb04d8 079c:trace:seh:dispatch_exception esi=0edac800 edi=003534a0 cs=0023 ds=002b es=002b fs=0063 gs=006b ss=002b 079c:trace:seh:call_seh_handlers calling handler at 79831DE9 code=80000003 flags=0 079c:trace:seh:call_seh_handlers handler at 79831DE9 returned 1 079c:trace:seh:call_seh_handlers calling handler at 798523DA code=80000003 flags=0 079c:trace:seh:call_seh_handlers handler at 798523DA returned 1 079c:trace:seh:call_seh_handlers calling handler at 79814720 code=80000003 flags=0 079c:trace:seh:call_seh_handlers handler at 79814720 returned 1 079c:trace:seh:call_seh_handlers calling handler at 7BD398F0 code=80000003 flags=0 079c:trace:seh:__regs_RtlUnwind code=80000003 flags=2 079c:trace:seh:__regs_RtlUnwind eip=7bd0cf6a esp=0edab96c ebp=0edab974 eflags=00000216 079c:trace:seh:__regs_RtlUnwind eax=00000000 ebx=0edac848 ecx=80000003 edx=0edac848 079c:trace:seh:__regs_RtlUnwind esi=7ffb2000 edi=0edaba88 cs=0023 ds=002b es=002b fs=0063 gs=006b ss=002b 079c:trace:seh:__regs_RtlUnwind calling handler at 7BD5E1A0 code=80000003 flags=2 079c:trace:seh:__regs_RtlUnwind handler at 7BD5E1A0 returned 1 079c:trace:seh:__regs_RtlUnwind calling handler at 79831DE9 code=80000003 flags=2 079c:trace:seh:__regs_RtlUnwind handler at 79831DE9 returned 1 079c:trace:seh:__regs_RtlUnwind calling handler at 798523DA code=80000003 flags=2 079c:trace:seh:__regs_RtlUnwind handler at 798523DA returned 1 079c:trace:seh:__regs_RtlUnwind calling handler at 79814720 code=80000003 flags=2 079c:trace:seh:__regs_RtlUnwind handler at 79814720 returned 1 079c:trace:seh:dispatch_exception code=c0000005 (EXCEPTION_ACCESS_VIOLATION) flags=0 addr=03E7C976 079c:trace:seh:dispatch_exception info[0]=00000000 079c:trace:seh:dispatch_exception info[1]=00000048 079c:trace:seh:dispatch_exception eip=03e7c976 esp=0edac1bc ebp=0edac294 eflags=00010212 079c:trace:seh:dispatch_exception eax=00000000 ebx=003533e0 ecx=00000000 edx=0e60d194 079c:trace:seh:dispatch_exception esi=0edac800 edi=0edac294 cs=0023 ds=002b es=002b fs=0063 gs=006b ss=002b 079c:trace:seh:call_seh_handlers calling handler at 07898521 code=c0000005 flags=0 079c:trace:seh:call_seh_handlers handler at 07898521 returned 1 079c:trace:seh:call_seh_handlers calling handler at 79B69550 code=c0000005 flags=0 079c:trace:seh:call_seh_handlers handler at 79B69550 returned 1 079c:trace:seh:call_seh_handlers calling handler at 79B69550 code=c0000005 flags=0 079c:trace:seh:call_seh_handlers handler at 79B69550 returned 1 079c:trace:seh:call_seh_handlers calling handler at 7BD398F0 code=c0000005 flags=0 079c:trace:seh:__regs_RtlUnwind code=c0000005 flags=2 079c:trace:seh:__regs_RtlUnwind eip=7bd0cf6a esp=0edab52c ebp=0edab534 eflags=00000212 079c:trace:seh:__regs_RtlUnwind eax=00000000 ebx=0edac848 ecx=c0000005 edx=0edac848 079c:trace:seh:__regs_RtlUnwind esi=7ffb2000 edi=0edab648 cs=0023 ds=002b es=002b fs=0063 gs=006b ss=002b 079c:trace:seh:__regs_RtlUnwind calling handler at 7BD5E1A0 code=c0000005 flags=2 079c:trace:seh:__regs_RtlUnwind handler at 7BD5E1A0 returned 1 079c:trace:seh:__regs_RtlUnwind calling handler at 07898521 code=c0000005 flags=2 079c:trace:seh:__regs_RtlUnwind handler at 07898521 returned 1 079c:trace:seh:__regs_RtlUnwind calling handler at 79B69550 code=c0000005 flags=2 079c:trace:seh:__regs_RtlUnwind handler at 79B69550 returned 1 079c:trace:seh:__regs_RtlUnwind calling handler at 79B69550 code=c0000005 flags=2 079c:trace:seh:__regs_RtlUnwind handler at 79B69550 returned 1 -- Do not reply to this email, post in Bugzilla using the above URL to reply. You are receiving this mail because: You are watching all bug changes.
https://bugs.winehq.org/show_bug.cgi?id=56829 --- Comment #12 from mushu <csumushu(a)126.com> --- (In reply to Eric Pouech from comment #9)
Method 3 can solve the problem. Why is that so? these .pdb files contain symbolic debug information, which are loaded by dbghelp likely something goes wrong it this process
Because my program encountered a stack overflow issue, but previously, this issue was resolved by deleting the PDB file, which resulted in the inability to print function information when an exception occurred. Now, I have to address this problem. How should I analyze it? -- Do not reply to this email, post in Bugzilla using the above URL to reply. You are receiving this mail because: You are watching all bug changes.
https://bugs.winehq.org/show_bug.cgi?id=56829 --- Comment #13 from Eric Pouech <eric.pouech(a)gmail.com> --- (In reply to mushu from comment #12)
(In reply to Eric Pouech from comment #9)
Method 3 can solve the problem. Why is that so? these .pdb files contain symbolic debug information, which are loaded by dbghelp likely something goes wrong it this process
Because my program encountered a stack overflow issue, but previously, this issue was resolved by deleting the PDB file, which resulted in the inability to print function information when an exception occurred. Now, I have to address this problem. How should I analyze it?
from #12, the following lines 079c:fixme:dbghelp_msc:codeview_get_type Returning NULL symt for type-id 11fe 079c:fixme:dbghelp_msc:pdb_global_feed_types S-Udt "tagDHCP4RShellCallbackSet": couldn't find type 0x11fe 079c:fixme:dbghelp_msc:codeview_get_type Returning NULL symt for type-id 10a4 079c:fixme:dbghelp_msc:pdb_global_feed_types S-Udt "_CMSCBB_CALLBACK_FUNCS": couldn't find type 0x10a4 079c:fixme:dbghelp_msc:codeview_get_type Returning NULL symt for type-id 113c1 079c:fixme:dbghelp_msc:pdb_global_feed_types S-Udt "cmscbb_ctx_create_params_st": couldn't find type 0x113c1 079c:fixme:dbghelp_msc:codeview_get_type Returning NULL symt for type-id 11457 079c:fixme:dbghelp_msc:pdb_global_feed_types S-Udt "cmscbb_sys_plantform_funcs_st": couldn't find type 0x11457 079c:trace:dbghelp_symt:symt_new_compiland Adding compiland symbol L"winosp":"* CIL *" also show some issues with type management (and that's likely the same cause as the one that triggers the assertion) some options: - comment out the assert() clause in dbghelp/symbol.c (the patch attached the other bug issue mentionned in #7 would likely do). If the crash doesn't involve the symbols which have type issue, you could get further in the backtrace. - if you can recompile the failing program (winosp.exe), you can try to relink it without incremental linking (/INCREMENTAL:NO iirc the option). In some cases incremental linking generates some complex constructs that Wine dbghelp doesn't fully support, - is the failing program (winosp.exe + attached .pdb files) available somewhere? If possible, I'd like to investigate the .pdb files (but these can contain some sensitive information) -- Do not reply to this email, post in Bugzilla using the above URL to reply. You are receiving this mail because: You are watching all bug changes.
https://bugs.winehq.org/show_bug.cgi?id=56829 --- Comment #14 from mushu <csumushu(a)126.com> --- (In reply to Eric Pouech from comment #13)
(In reply to mushu from comment #12)
(In reply to Eric Pouech from comment #9)
Method 3 can solve the problem. Why is that so? these .pdb files contain symbolic debug information, which are loaded by dbghelp likely something goes wrong it this process
Because my program encountered a stack overflow issue, but previously, this issue was resolved by deleting the PDB file, which resulted in the inability to print function information when an exception occurred. Now, I have to address this problem. How should I analyze it?
from #12, the following lines 079c:fixme:dbghelp_msc:codeview_get_type Returning NULL symt for type-id 11fe 079c:fixme:dbghelp_msc:pdb_global_feed_types S-Udt "tagDHCP4RShellCallbackSet": couldn't find type 0x11fe 079c:fixme:dbghelp_msc:codeview_get_type Returning NULL symt for type-id 10a4 079c:fixme:dbghelp_msc:pdb_global_feed_types S-Udt "_CMSCBB_CALLBACK_FUNCS": couldn't find type 0x10a4 079c:fixme:dbghelp_msc:codeview_get_type Returning NULL symt for type-id 113c1 079c:fixme:dbghelp_msc:pdb_global_feed_types S-Udt "cmscbb_ctx_create_params_st": couldn't find type 0x113c1 079c:fixme:dbghelp_msc:codeview_get_type Returning NULL symt for type-id 11457 079c:fixme:dbghelp_msc:pdb_global_feed_types S-Udt "cmscbb_sys_plantform_funcs_st": couldn't find type 0x11457 079c:trace:dbghelp_symt:symt_new_compiland Adding compiland symbol L"winosp":"* CIL *" also show some issues with type management (and that's likely the same cause as the one that triggers the assertion)
some options: - comment out the assert() clause in dbghelp/symbol.c (the patch attached the other bug issue mentionned in #7 would likely do). If the crash doesn't involve the symbols which have type issue, you could get further in the backtrace. - if you can recompile the failing program (winosp.exe), you can try to relink it without incremental linking (/INCREMENTAL:NO iirc the option). In some cases incremental linking generates some complex constructs that Wine dbghelp doesn't fully support, - is the failing program (winosp.exe + attached .pdb files) available somewhere? If possible, I'd like to investigate the .pdb files (but these can contain some sensitive information)
Thank you for your reply. I tried the first method but it still didn’t work. However, I found a solution: in the wine environment, only the address was printed without the function name. By obtaining the base address of the program loaded by wine, I was able to calculate the address offset, which could then be converted back to an address in windbg. This allowed me to retrieve the function name. -- Do not reply to this email, post in Bugzilla using the above URL to reply. You are receiving this mail because: You are watching all bug changes.
participants (1)
-
WineHQ Bugzilla