help in debugging

[Damjan Jovanovic]

On 2/5/07, Ioannis Nousias <s0238762 at sms.ed.ac.uk> wrote:
> Hello Wine developers,
>
> I've decided to see what causes floAt's Mobile Agent[1] to fail with wine
>
> I checked the wine developers' cheatsheet to help me debug the
> application, but I'm lost.
>
> The application installs but with some error:
> "C:\Program Files\Fma\sframeword\helper\BramusICQ.dll
> Unable to register the DLL/OCX: LoadLibrary failed; code 126
> Module not found."

Can you try typing
$ regsvr32 BramusICQ.dll
manually? You'll have to do it from the directory it's in.

> I click "ignore" and the installation continues. When I try to execute
> the installed binary "MobileAgent.exe" it fails.
>
> I invoke it like this:
>
> WINEDEBUG=+seh,+relay WINEPREFIX=/tmp/winetemp wine MobileAgent.exe
>
> no error messages are produce by the app itself.
>
> on wine's debug log I see the following, just before winedbg starts:
>
> 0009:Ret  kernel32.SetEvent() retval=00000001 ret=00410759
> trace:seh:call_stack_handlers handler at 0x4045c7 returned 1
> trace:seh:call_stack_handlers calling handler at 0x477d9a code=eedfade
> flags=1
> 0009:Call ntdll.RtlUnwind(0034feb8,0040427c,0034f140,00000000) ret=0040427c
> 0009:  eax=0034f140 ebx=0034eca0 ecx=005acb61 edx=0034feb8 esi=0034feb8
> edi=00000001 ebp=0034ecb8 esp=0034ec6c ds=007b es=007b fs=0033 gs=003b
> flags=
> 00200246
> trace:seh:__regs_RtlUnwind code=eedfade flags=3
> trace:seh:__regs_RtlUnwind calling handler at 0x60178400 code=eedfade
> flags=3
> trace:seh:__regs_RtlUnwind handler at 0x60178400 returned 1
> 0009:Ret  ntdll.RtlUnwind() retval=00000000 ret=0040427c
> 0009:  eax=00000000 ebx=0034eca0 ecx=005acb61 edx=0034feb8 esi=0034feb8
> edi=00000001 ebp=0034ecb8 esp=0034ec6c ds=007b es=007b fs=0033 gs=003b
> flags=
> 00200246
> trace:seh:call_stack_handlers handler at 0x4045c7 returned 1
> trace:seh:call_stack_handlers calling handler at 0x69ff49 code=eedfade
> flags=1
> trace:seh:call_stack_handlers handler at 0x69ff49 returned 1
> trace:seh:call_stack_handlers calling handler at 0x4046b8 code=eedfade
> flags=1
> 0009:Call kernel32.UnhandledExceptionFilter(0034ec90) ret=004046dc
> wine: Unhandled exception 0x0eedfade at address 0x0000:0x6024daa0
> (thread 0009), starting debugger...
> trace:seh:start_debugger Starting debugger "winedbg --auto 8 228"
>
> this is not the first "trace:seh". Relatively early in the call stack
> there is this:
>
> 000b:Call user32.SetDeskWallPaper(code=c0000005 flags=0 addr=0x601b044b
> trace:seh:raise_exception  info[0]=00000000
> trace:seh:raise_exception  info[1]=ffffffff
> trace:seh:raise_exception  eax=ffffffff ebx=6011999c ecx=00000003
> edx=0000ffff esi=00000000 edi=ffffffff
> trace:seh:raise_exception  ebp=00117b98 esp=0034f61c cs=0073 ds=007b
> es=007b fs=0033 gs=003b flags=00010206
> trace:seh:call_stack_handlers calling handler at 0x602b5540
> code=c0000005 flags=0
> trace:seh:__regs_RtlUnwind code=c0000005 flags=2
> trace:seh:__regs_RtlUnwind calling handler at 0x602b5400 code=c0000005
> flags=2
> trace:seh:__regs_RtlUnwind handler at 0x602b5400 returned 1
> ffffffff (invalid)) ret=6033e95f
>
> which looks suspicious to me.
>
> Am I on the right track? Unfortunately I'm not familiar with windows API
> or wine's underlying architecture. I need some guidance please :) I'm an
> experienced C/C++ programmer.
>
> thanks
>
> -Ioannis
>
>
>
>
>
>
>
>
>
>
>
> [1] http://fma.sourceforge.net/index2.htm
>
>
>