RE: Is there any way to debug driver?

[Wang, Robin]

Hi Roderick,

Using winedbg, it is OK for us to break into libGL.so. But we cannot set break 
point in our dri drivers, which is loaded by libGL.so using dlopen().

Thanks,
Robin

-Original Message-
From: Roderick Colenbrander [mailto:thunderbir...@gmail.com] 
Sent: Monday, June 22, 2009 8:15 PM
To: Guan, Xiao-Feng
Cc: Ken Thomases; Wang, Robin; wine-devel; Boudier, Pierre; Zhou, Jesse; Jin, 
Jian-Rong; Sun, Sunny
Subject: Re: Is there any way to debug driver?

At what sort of points did you try to set breakpoints before? Note
that we are loading opengl dynamically which might make debugging a
little bit harder. What about plain winedbg? Today I tried 'winedbg
--gdb notepad' and indeed had some issues but plain winedbg worked
properly. Further 'gdb wine notepad' also worked properly except that
for some reason my back trace didn't include debug symbols.

It might help to explain what commands you are exactly using and what
sort of break points you attempt to set. Then we might be able to help
you better.

Roderick

On Mon, Jun 22, 2009 at 8:52 AM, Guan, Xiao-Feng wrote:
> The gdb way always turns into some SIGTRAP signal from preloader and
> finally terminates the loading process. It seems that the WINE binary
> loader would not co-work with gdb.
>
> We will try another way -- the WINE visual tests, to see if it is enough
> for work.
>
> Thanks very much.
>
> Guan Xiaofeng
> AMD Shanghai SW OpenGL Team
> 021-61601838-25746
> xiao-feng.g...@amd.com
>
>
> -Original Message-
> From: Ken Thomases [mailto:k...@codeweavers.com]
> Sent: Thursday, June 18, 2009 11:34 PM
> To: Wang, Robin; wine-devel
> Cc: Guan, Xiao-Feng; Boudier, Pierre; Zhou, Jesse; Jin, Jian-Rong; Sun,
> Sunny
> Subject: Re: Is there any way to debug driver?
>
> On Jun 17, 2009, at 10:49 AM, Wang, Robin wrote:
>
>> We also have tried using winedbg, but it cannot break into our
>> driver either.
>>
>> The only way we can break into our driver before is using "gdb wine-
>> pthread", but now it is not available.
>>
>> Do you have some suggestion on winedbg configuration to make it able
>> to break into graphics drivers.
>
> As already mentioned by Ben Klein, just try "gdb wine" instead of "gdb
> wine-pthread".  The executable name has changed.  That's all.
>
> Cheers,
> Ken
>
>
>
>
>
>

RE: Is there any way to debug driver?

[Wang, Robin]

We also have tried using winedbg, but it cannot break into our driver either.

The only way we can break into our driver before is using "gdb wine-pthread", 
but now it is not available.

Do you have some suggestion on winedbg configuration to make it able to break 
into graphics drivers.

Thanks

-Original Message-
From: Henri Verbeet [mailto:hverb...@gmail.com] 
Sent: Wednesday, June 17, 2009 9:27 PM
To: Guan, Xiao-Feng
Cc: wine-devel@winehq.org; Wang, Robin; Zhou, Jesse; Jin, Jian-Rong; Sun, 
Sunny; Boudier, Pierre
Subject: Re: Is there any way to debug driver?

2009/6/17 Guan, Xiao-Feng :
>   As we can see that, from version 1.1.23, all application fails to start on
> AMD card. We are going to investigate why it happens. If it is necessary,
> Would you please let us know a little more about the changes of this
> version?
>
There's a bug for that specific issue filed at
http://ati.cchtml.com/show_bug.cgi?id=1571. It contains an explanation
and test case. Current git versions of Wine avoid the bug by just not
attaching compressed and depth formats to an FBO, since they're not
supposed to be color-renderable anyway.

I'm afraid I can't help much with getting gdb working with Wine, I
don't use/like debuggers much. I think you're supposed to use winedbg
for Wine debugging though.

Henri