| Title: | DECmcc user notes file. Does not replace IPMT. |
| Notice: | Use IPMT for problems. Newsletter location in note 6187 |
| Moderator: | TAEC::BEROUD |
| Created: | Mon Aug 21 1989 |
| Last Modified: | Wed Jun 04 1997 |
| Last Successful Update: | Fri Jun 06 1997 |
| Number of topics: | 6497 |
| Total number of notes: | 27359 |
I asked this question in the CMA notes conference first but I realized
that my problems are due to the MCC jacket routines for threads.
How can I make the connection between mutexes, condition variables, and
thread handles as they appear in the debugger and all of these in my
application? If I examine a mutex and then use the CMA debugger to
list out mutexes, is there an easy way to match these up?
What about %TASK IDs and actual threads? Is there an easy way to
figure out what task corresponds to a thread?
A mapping from MCC thread objects to CMA thread objects would probably
be sufficient for me to proceed. Thanks.
John
| T.R | Title | User | Personal Name | Date | Lines |
|---|---|---|---|---|---|
| 2552.1 | mcc_thread_directory() | TOOK::BURGESS | Thu Mar 12 1992 17:33 | 33 | |
> How can I make the connection between mutexes, condition variables, and
> thread handles as they appear in the debugger and all of these in my
> application? If I examine a mutex and then use the CMA debugger to
> list out mutexes, is there an easy way to match these up?
>
mcc mutex handle = cma mutex handle
mcc condition variable handle = cma condition variable handle
As I replied earlier, the mcc thread id not-equal to cma thread handle-
partly because of historical reasons, partly because MCC needs
extra data structure anyway.
There are some undocumented routines in the mcc kernel which
you can invoke from the debbuger to dump info about mcc threads
mcc_thread_directory()
prints a table of mcc threads and attribute values,
including the mcc thread id and the cma handle low order
longword which is the %task value
fw_thread_show(fw_t_tsv *p_tsv)
prints all the attributes for a particular thread
> What about %TASK IDs and actual threads? Is there an easy way to
> figure out what task corresponds to a thread?
>
> A mapping from MCC thread objects to CMA thread objects would probably
> be sufficient for me to proceed. Thanks.
>
>
| |||||
| 2552.2 | QUIVER::DESMOND | Thu Mar 12 1992 18:00 | 3 | ||
Thanks. The mcc_thread_directory call is just what I needed.
John
| |||||