Sylvain Petreolle wrote:
After doing a 'wineserver -k', some wine processes arent stopped.
Using winedbg and doing a 'walk process' (which starts another wineserver) is currently unable to see the wine processes that were created before.
that's normal. winedbg is running (as a process) in the second (still alive) wineserver. There's no way it can connect to the (now) defuncted first wineserver (you just killed the server) and then get the process list.
use gdb and the attach command on the unix pid of the still running wine processes to see where they are hung
A+