wine users - Dec 2010 - How to debug driver code when app run on wine?

I am trying to debug opengl driver when windows Direct3D game runs on wine, and
encounter the problem

Working on SUSE 11.2, and download the wine binary by YaST2, then:

root>gdb wine
gdb> b driver_init
gdb> r game.exe

then I can break the driver on driver_init, and i can see the driver stack by
bt, but I cannot see the driver source code, debugger can not find the source
code file, but if you use "s" to step by step, debugger can find each
function called, so it's strange.

So am I doing right for debugging this case, I am new to wine, thanks in advance

On 12/25/10 6:49 PM, jeffliu wrote:
> I am trying to debug opengl driver when windows Direct3D game runs on wine,
and encounter the problem
>
Are you trying to debug the opengl code used by Wine?

What program are you trying to run and what is the output when you run 
it from the command line (http://wiki.winehq.org/FAQ#run_from_terminal)?

If the output is quite lengthy, you should save it to a file and then 
post it to a site like pastebin.com, and then post the URL here.

Thank you.

James McKenzie

jeffliu wrote:
> I am trying to debug opengl driver when windows Direct3D game runs on wine,
and encounter the problem
> 
> Working on SUSE 11.2, and download the wine binary by YaST2, then:
> 
> root>gdb wine
> gdb> b driver_init
> gdb> r game.exe
> 
> then I can break the driver on driver_init, and i can see the driver stack
by bt, but I cannot see the driver source code, debugger can not find the source
code file, but if you use "s" to step by step, debugger can find each
function called, so it's strange.
> 
> So am I doing right for debugging this case, I am new to wine, thanks in
advance


Or do I have to build wine from source code to debug this?

I am trying to debug opengl driver when windows Direct3D game runs on wine,
and encounter the problem?

Working on SUSE 11.2, and download the wine binary by YaST2, then:

root>gdb wine
gdb> b driver_init
gdb> r game.exe

then I can break the driver on driver_init, and i can see the driver stack
by bt, but I cannot see the driver source code, debugger can not find the
source code file, but if you use "s" to step by step, debugger can
find each
function called, so it's strange.

So am I doing right for debugging this case, I am new to wine, thanks in
advance?

Or should I build wine from source code to debug this?

Thanks
Jeff Liu
-------------- next part --------------
An HTML attachment was scrubbed...
URL:
<http://www.winehq.org/pipermail/wine-users/attachments/20101226/a56a9bab/attachment.htm>