How to detect a cygwin thread?

Mark Geisert
Sun May 10 00:50:00 GMT 2009

Piotr Wyderski writes:
> My program has a built-in panic handler, which enumerates
> all process threads using the CreateToolhelp32Snapshot
> WinAPI function and then suspends them (except itself)
> in order to freeze the entire environment in a state as close
> as possible to the original error conditions. Unfortunately it
> also stops the internal Cygwin thread (which seems to spend
> most of its time in cygwin1.dll!toascii+0x15d0) and the entire
> process hangs. Is there a way to identify those Cygwin
> threads in order not to suspend them?

Why assume Cygwin could be the only source of extra threads?

Wouldn't it make more sense to have your program remember its own threads and
only suspend those?  Presumably you know when and where your program's threads
are created and destroyed, right?


Unsubscribe info:
Problem reports:

More information about the Cygwin mailing list