On 2/21/07, maarten Kooiker <mckooiker@xxxxxxxxx> wrote:
Lately I get some problems when I run the command WINEDEBUG=+seh,+trace wine <program_name> 2>log Practically I get the following log: trace:relay:init_debug_lists RelayExclude = L"ntdll.RtlEnterCriticalSection ;ntdll.RtlLeaveCriticalSection;kernel32.94;kernel32.95;kernel32.96;kernel32.97;kernel32.98" trace:relay:init_debug_lists RelayFromExclude = L"winex11.drv;user32;gdi32;advapi32;kernel32" 0009:Call kernel32.__wine_kernel_init() ret=7bc39e98 0009:Call PE DLL (proc=0x7eba54f0,module=0x7eb80000 L"advapi32.dll",reason=WINE_PREATTACH,res=(nil)) 0009:Ret PE DLL (proc=0x7eba54f0,module=0x7eb80000 L"advapi32.dll",reason=WINE_PREATTACH,res=(nil)) retval=1 followed by an enormous amount of ''call'' and ''ret'' messages. The programms work fine, so problem seems not to be very urgent.... I attach a log-file of a program that works fine (notepad, just to keep things simple).
If your apps work fine, why are you running wine with debugging turned on (WINEDEBUG=...)? -- James Hawkins _______________________________________________ wine-users mailing list wine-users@xxxxxxxxxx http://www.winehq.org/mailman/listinfo/wine-users
