Piotr Wyderski wrote:
> Christopher Faylor wrote:
>
>> The closest API to it would be a call to
>> cygwin_internal(CW_GETTHREADNAME, <windows-thread-id>);
>
> Now it works like a charm. The internal thread
> which suspension leads to program hangup
> is named "sig".
This is the signal-listener thread that all cygwin processes start, to
handle signals for them while they may be busy in blocking win32 calls.
Is there a POSIX way of doing what you want?
cheers,
DaveK
--
Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple
Problem reports: http://cygwin.com/problems.html
Documentation: http://cygwin.com/docs.html
FAQ: http://cygwin.com/faq/
