[Bug 16941] interrupts cause nested trace output

wine-bugs at winehq.org wine-bugs at winehq.org
Fri Jun 12 03:54:20 CDT 2009


http://bugs.winehq.org/show_bug.cgi?id=16941





--- Comment #7 from Jörg Höhle <hoehle at users.sourceforge.net>  2009-06-12 03:54:19 ---
Created an attachment (id=21749)
 --> (http://bugs.winehq.org/attachment.cgi?id=21749)
3 log samples from around raise_exception

When "The Westerner" crashes after the intro, there's a slight variation of
nested logs. Looking closely, it seems a part of a former log line is
duplicated.

The normal exception log header line is:
trace:seh:raise_exception code=c000013a flags=0 addr=0x7ef9400d ip=7ef9400d
tid=0009

A weird one looks like follows, with the code=... part lacking the
raise_exception prefix, and attached to another line instead:
Ret  msadp32.acm.DriverProc() retval=00000001 ret=7e4569b6
 get_console_input_info( handle=0000 )
 get_console_input_info() = INVALID_PARAMETER { history_mode=0, history_size=0,
history_index=0, edition_mode=0, input_cp=0, output_cp=0, win=00000000,
title=L"" }
Ret  msadp32.acm.DriverProc()code=c000013a flags=0 addr=0xb8053430 ip=b8053430
tid=0009
trace:seh:raise_exception  eax=00000040 ebx=00000002 ecx=7efff0c8 edx=00000040
esi=0000001e edi=0000001e

Do you see how the prefix "Ret  msadp32.acm.DriverProc()" seems duplicated and
replacing the raise_exception part?

Attached are 2-3 larger samples of this, all from The Westerner. This is not
yet enough material to open another issue, so I'm just leaving a note here.

BTW, where does get_console_input come from? Is that the exception handling
code already kicking in?

This was produced using wine-1.1.22, compiled by me on Ubuntu 8.04 (or 8.10?).

-- 
Configure bugmail: http://bugs.winehq.org/userprefs.cgi?tab=email
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.


More information about the wine-bugs mailing list