Robert Shearman wrote:
I've experienced the same thing on a perfectly clean kernel (I think 2.6.5-mm1), but I assumed it was because we were messing around with signals. If I can reproduce the problem I will report it, although Mike McCormack seems to have had quite a bit of contact already with the kernel folks ;)
Rob
Hey Rob,
The problem seems to be a kernel bug. It's been round since 2.6.0... in my experience it only seems to happen when you terminate a wine process using ^C or when the program crashes tries to start the debugger, fails, then you press ^C
Mike