[Info-vax] HIBertanting DECthreads process accrues CPU time.

[VAXman- at SendSpamHere.ORG]

In article <5c565fb6-35f4-43cb-9d74-0dff5efd9f6b at d16g2000yqd.googlegroups.com>, San <rsandeep80 at gmail.com> writes:
>
>> I'm trying to get the trcWriteIV ( ) after this to produce some output
>> but I've not gotten the proper incantation. =A0Can you advise? =A0I'm als=
>o
>> confuse as to where the OTS$MOVE, which appears in the PRF PC trace, is
>> coming into play.
>>
>
>Traces are turned off, by default. To turn it on, the library needs to
>be re-compiled.
>I could see a lot of "unwind" code in the PC sampling. So someone is
>trying to
>unwind the stack. It would be interesting to know who is doing that.

Interesting.  I have established EXE$SIGTORET to return errors instead
of signaling them.  Perhaps, I could remove them and I might see some-
thing cough up an exception.  I don't have anything issuing an $UNWIND
in this code that *I* have explicitly written into it.

-- 
VAXman- A Bored Certified VMS Kernel Mode Hacker    VAXman(at)TMESIS(dot)ORG

All your spirit rack abuses, come to haunt you back by day.
All your Byzantine excuses, given time, given you away.