Found it! - run a wineapp do a ps see if you have wine-pthread or wine-kthread running - Lets say it is wine-pthread than at gdb do - (gdb) file wine-pthread
and off you go. what happened is that gdb got the processes switched on him mid run. I think there should be a way to follow the next process but I couldn't figure how.
In any way what I did was link -s my wine to wine-ptread (didn't want to change all these kdevelop projects :) ). Maybe there should be an Installation option that Auto-detects the Auto-detected-wine variant and soft link to it.
Gregory M. Turner wrote:
On Saturday 13 December 2003 10:39 am, Mike Hearn wrote:
Hi,
Running wine in gdb appears to be broken with latest CVS:
(gdb) file wine Reading symbols from wine...done. Using host libthread_db library "/lib/tls/libthread_db.so.1". (gdb) run Starting program: /opt/wine/bin/wine wine [Thread debugging using libthread_db enabled] [New Thread -1084455552 (LWP 30661)] [New Thread -1084458064 (LWP 30662)] Cannot find user-level thread for LWP 30661: generic error
This is on fedora core 1. It looks like it might be the NPTL runtime
detection stuff, does anybody have any ideas?
heh, same here :P
