Hello Markus.
I think this is exactly what is going wrong.
It fits the description of what i am seeing.
The kernel man-pages even go so far as to state:
"The effects of this call in a multi-threaded process are unspecified."
http://linux.die.net/man/2/signal
So i guess using signal() inside wine
Peter Dons Tychsen wrote:
> Hello.
>
> It starting with me trying to figure out why i was loosing keyboard
> events in winedos.
>
> 1) I then traced the keyboard events to a call to signal(SIGUSR2) in
> function DOSVM_QueueEvent().
>
> 2) The signal() triggers code in ntdll, which generates an e
Hello.
It starting with me trying to figure out why i was loosing keyboard
events in winedos.
1) I then traced the keyboard events to a call to signal(SIGUSR2) in
function DOSVM_QueueEvent().
2) The signal() triggers code in ntdll, which generates an exception
EXCEPTION_VM86_STI for the current
