Regarding Wine Debugging

Open forum for end-user questions about Wine. Before asking questions, check out the Wiki as a first step.
Forum Rules
Locked
sainath
Level 2
Level 2
Posts: 18
Joined: Tue Sep 30, 2008 1:16 am

Regarding Wine Debugging

Post by sainath »

when we use WINEDEBUG=trace+relay ,it shows function calls of all dlls.
but,when a function is called in a dll ,it may call some other functions internally before return.
What is the channel we have to use to know the those function calls and their return values.

In the log report of WINEDEBUG=trace+relay there are two variables "retval" and "ret".
what is their significance?
vitamin
Moderator
Moderator
Posts: 6605
Joined: Sat Feb 23, 2008 2:29 pm

Re: Regarding Wine Debugging

Post by vitamin »

sainath wrote:What is the channel we have to use to know the those function calls and their return values.
If this is builtin dll then you already have that - "relay" channel shows all function calls with few exceptions. BUT by default internal calls to winex11.drv, user32, gdi32, advapi32 and kernel32 are excluded - see [HKCU\Software\Wine\Debug\RelayFromExclude] registry key.

For native dlls you can use +snoop channel. However in some cases it can break execution of a program. So keep that in mind when things stop working.
sainath wrote:In the log report of WINEDEBUG=trace+relay there are two variables "retval" and "ret". what is their significance?
ret - returning address (next command after "call").
retval - returned value from the function.
Locked