Re: why I cannot use winedbg --gdb

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

 



Thanks vitamin. using gdb start wine-pthread make everything work fine. it solved the problem which puzzled me several weeks. But I do not see any article mentioned it in wine development doc.

Thanks a lot!!!




cikka wrote:
> 
> vitamin wrote:
> > 
> > cikka wrote:
> > > whan can result to gdb proxy broken, How can I solve it.
> > 
> > Start hacking Wine. You can't magically fix it.
> > 
> > 
> > cikka wrote:
> > > and when I use winedbg to debug, I cannot print the vaule of the local variable some times.  why?
> > 
> > 
> > Should work. If if doesn't - file a bug report with exact steps to reproduce.
> > 
> > Your best bet would be to start Wine process suspended (or add a long long sleep somewhere at the start). Then attach to it with gdb.
> > You can also directly run Wine under gdb. You just have to start wine-pthread not wine. See developer's doc for more options and other details.
> 
> 
> 
> Thanks!  Which thread should I attach with gdb if I want to debug into libgl.so. When I use command "ps -e", there are many thread related to wine, e.g.wineserver; device.exe; app.exe; etc.
> I have tried attach every thread, it seems neither can make me break into libgl.so.
> 
> Thanks!!







[Index of Archives]     [Gimp for Windows]     [Red Hat]     [Samba]     [Yosemite Camping]     [Graphics Cards]     [Wine Home]

  Powered by Linux