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:[email protected]] Sent: Wednesday, June 17, 2009 9:27 PM To: Guan, Xiao-Feng Cc: [email protected]; 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 <[email protected]>: > 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
