Winedbg not seeing 'orphaned' wine processes
spetreolle at yahoo.fr
Wed Sep 17 21:13:13 CDT 2003
After doing a 'wineserver -k', some wine processes arent stopped.
Using winedbg and doing a 'walk process' (which starts another
is currently unable to see the wine processes that were created before.
[syl at snoop bin]$ ps -efl |grep wine
0 S syl 26355 1 0 75 0 - 41016 schedu 04:01 pts/4
00:00:00 /usr/local/bin/wine wcmd
0 S syl 26709 26208 0 75 0 - 909 pipe_w 04:11 pts/4
00:00:00 grep wine
And winedbg says there is no process :
[syl at snoop bin]$ winedbg
fixme:console:SetConsoleCtrlHandler (0x4063f068,1) - no error checking
or testing yet
WineDbg starting on pid 0
pid threads parent executable
Can this process be debugged in any way or is it completely unreachable ?
Sylvain Petreolle (spetreolle_at_users_dot_sourceforge_dot_net)
Say NO to software patents
Dites NON aux brevets logiciels
"What if tomorrow the War could be over ?" Morpheus, in "Reloaded".
Do You Yahoo!? -- Une adresse @yahoo.fr gratuite et en français !
Yahoo! Mail : http://fr.mail.yahoo.com
More information about the wine-devel