https://bugs.winehq.org/show_bug.cgi?id=57675 --- Comment #1 from mushu <csumushu(a)126.com> --- I modified the Wine code to call backtrace in virtual_setup_exception to print the call stack. The content is as follows: /usr/local/bin/../lib/wine/i386-unix/ntdll.so(+0x5c5b1) [0xf7cbe5b1] /usr/local/bin/../lib/wine/i386-unix/ntdll.so(+0x644d4) [0xf7cc64d4] /usr/local/bin/../lib/wine/i386-unix/ntdll.so(+0x3f796) [0xf7ca1796] /usr/local/bin/../lib/wine/i386-unix/ntdll.so(+0x3fe59) [0xf7ca1e59] linux-gate.so.1(__kernel_rt_sigreturn+0) [0xf7fc3090] [0x7bd5b54c] [0x7bd3b539] [0x7b685c57] [0x7b679f1c] [0x7b685cdb] [0x7b6671f5] [0x7bd398c8] [0x7bd0cf3d] [0x7bd0cf0f] [0x7bd3f96c] [0x7bd4190a] [0x7bd0cd65] [0x7b670212] [0x45f83f] I can resolve the symbols for the ntdll part, which are: segv_handler -> setup_raise_exception -> virtual_setup_exception -> print_stack_trace. Is there a way to determine what the call stack below represents? -- 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.