ntdll: Fix SIGTRAP handling

[Alexandre Julliard]

Petr Tesarik <hat at tesarici.cz> writes:

> That means that Windows XP creates a new thread in the given process
> and breaks it at DbgBreak().
>
> Does this mean that we may avoid sending SIGTRAP altogether?

Creating a new thread is probably even harder, but yes we can
certainly avoid SIGTRAP. One possible way is to use SIGUSR1 to change
the thread context to simulate a call to DbgBreakPoint.

-- 
Alexandre Julliard
julliard at winehq.org