This is the mail archive of the
mailing list for the Cygwin project.
Re: Is multithreaded profiling on cygwin possible?
- From: Corinna Vinschen <corinna-cygwin at cygwin dot com>
- To: cygwin at cygwin dot com
- Date: Wed, 15 Oct 2003 12:11:14 +0200
- Subject: Re: Is multithreaded profiling on cygwin possible?
- References: <firstname.lastname@example.org>
- Reply-to: cygwin at cygwin dot com
On Wed, Oct 15, 2003 at 05:57:31PM +0800, peter garrone wrote:
> Brian Ford wrote:
> >On Tue, 14 Oct 2003, peter garrone wrote:
> >> A list of active threads is maintained. A thread calling moncontrol(1) gets
> >> put in the list. When a call to SuspendThread fails, the thread is assumed
> >> to be defunct and taken off the list.
> >Seems reasonable.
> >I guess I was originally thinking "just profile all threads all the
> >time", but I guess you method is more flexable. That could
> >probably be an option somehow after you polish this up.
> There is no other way to detect a dead thread. Nothing like "atexit" or
> anything I could find anyway in the win32 api, of which my experience
> is limited, and ordinary.
WaitForSingleObject and friends. A terminated thread is in signalled
Corinna Vinschen Please, send mails regarding Cygwin to
Cygwin Developer mailto:email@example.com
Red Hat, Inc.
Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple
Problem reports: http://cygwin.com/problems.html