This is the mail archive of the
ecos-discuss@sources.redhat.com
mailing list for the eCos project.
Re: thread id
- From: Robin Singh <robin_singh at gmx dot net>
- To: Aravind B <arvindb at cranessoftware dot com>
- Cc: ecos <ecos-discuss at sources dot redhat dot com>
- Date: Wed, 08 Sep 2004 14:32:53 +0530
- Subject: Re: [ECOS] thread id
- References: <1094630011.9112.9.camel@ambica>
Hi.
On Wed, 2004-09-08 at 13:23 +0530, Aravind B wrote:
> Hello all,
>
> In my design 3 threads are running.
> t1, t2,and t3.
> suppose thread t1 is blocked using flag.
> After sometime t2 enables it.
> now how do i come to know which thread enabled t1.
>
One way would be to enable Instrumentation in your configuration and
look at the diagnostic output log. For binary semaphores atleast, there
seems to be sufficient information emitted which can be correlated to
figure out the owner of a semaphore which was posted to etc. May help
you.
The quickest way would be to rely on breakpoints! Tracing into the
scheduler code etc.
PS: I notice that there are no CYG_INSTRUMENT_* macro calls in the
flag.cxx code. Shouldn't they be there ? Anyone ?
--
Before posting, please read the FAQ: http://ecos.sourceware.org/fom/ecos
and search the list archive: http://ecos.sourceware.org/ml/ecos-discuss