[Info-vax] The PWAIT tool.

[VAXman- at SendSpamHere.ORG]

In article <jW2xm.11964$U5.164254 at newsb.telia.net>, =?ISO-8859-1?Q?Jan-Erik_S=F6derholm?= <jan-erik.soderholm at telia.com> writes:
>Hi.
>
>I have a process that is in "MUTEX" state.
>
>I found some tool called PWAIT and tried that.
>It runs inside of SDA (after DEFINE PWAIT$SDA to point
>to the PWAIT$SDA.EXE) like this :
>
>$ ana/sys
>
>OpenVMS system analyzer
>
>SDA> pwait SYMBIONT_669
>PWAIT V1.0 (c) 2004, Ian Miller (miller at encompasserve.org)
>built on VMS V8.2
>reading symbol tables
>%SDA-W-LINKTIMEMISM, link time of SYS$COMMON:[SYS$LDR]ERRORLOG.STB;1
>( 3-DEC-2004 09:50) does not match link time of image in system
>(18-JUL-2006 14:39)
>Process PID 000261DC name SYMBIONT_669 No. Threads 1
>Thread 0: state MWAIT AST pending KU active (none) blocked (none)

Mutext WAIT state with AST pending (I'm going to assume that Ian's 
KU means a special-kernel USER mode AST).


>Process has been waiting for 00:00:00.18
>Process thread resource wait is ENABLED
>Analyzing process locks
>         Process owns no locks
>         waiting for mutex 824A7E00

That's the address of the MUTEX.

You might try to EXAMINE 824A7E00 or MAP 824A7E00.  It might lend some
more insight as to what the mutex is that it is waiting on.

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

  http://www.quirkfactory.com/popart/asskey/eqn2.png
  
  "Well my son, life is like a beanstalk, isn't it?"