PROBLEM: (86047, 88167, 88641, 91259) (PATCH ID: OSF520-394)
********
This patch fixes three problems that can occur while debugging kernels 
with kdbx.
1. When kdbx is invoked it reports token length warnings
   prior to issuing a prompt.  An example is shown below.

   # kdbx -k /vmunix
   dbx version 5.1
   Type 'help' for help.

   thread 0xfffffc007fe16a80 stopped at  [thread_block:3211 ,0xfffffc00002e736c
   warning: Files compiled -g3: parameter values probably wrong
   Maximum token length exceeded
   Didn't consume last input
   Maximum token length exceeded
   Didn't consume last input
   (kdbx) 

2. The kdbx "ofile" command fails when verbose output is requested with -v.
   For example,

   (kdbx) ofile -pid 613314 -v
 
   Proc=0xfffffc0032056cc0   pid=613314 

    ADDR_FILE   f_cnt  ADDR_VNODE V_TYPE  V_TAG   USECNT V_FLAG  V_MOUNT    INO
   =========== ====== =========== ====== ======= ======= ====== =========== ===
   (kdbx) pid 613337 exited with signal SIGSEGV

3. Spurious warnings are reported when kdbx commands such as "u" and "ofile"
   are executed.  These warnings always begin with "add_type" and are similar 
   to the example shown below:

   add_type addr 0xfffffc0042129020, data 0x14001b620, both should be NULL in
   type "uid_t"

PROBLEM: (93714, 92650, 92648, KMF, 92212, 83371, 94138)
         (PATCH ID: OSF520-732)

PROBLEM: Not all audit data in the log is displayed after being sorted.
PROBLEM: System panic in audit_rec_build.
PROBLEM: Setting select/deselect flag on a directory does not affect if
an audit event is generated (with obj select/obj deselect) when an audited
file operation is performed.
PROBLEM: (95447) (PATCH ID: OSF520-912)
********
This patch fixes problems in the kdbx 'u' and 'vnode' extensions.
'u' extension failure

        The kdbx 'u' extension previously failed when invoked with a procedure
        address, causing the following kdbx error message:

        # kdbx -k /vmunix
        (kdbx) u 0xfffffc0004118cc0                                            
        Instance of x-> where x is struct or union and not pointer.
        ".stack->uthread->np_uthread"
        field .stack->uthread->np_uthread: trying to get the value of a
        zero size datum pid 1174 exited with status 1

        This problem has been fixed. The 'u' structure identified by the
        procedure address will now be displayed.

'vnode' extension user and group ID mismatch

        Previously, the 'vnode' extension's '-u <uid>' and '-g <gid>' options
        listed ADVFS vnodes that did not match the given user or group IDs.
        This condition appeared when running the kdbx 'vnode' extension on a 
        machine with ADVFS file systems that were not cluster members.  

        In the following example, two vnodes should have been listed that
        match user ID 1939.  Instead, all of the ADVFS (VT_MSFS) vnodes
        were listed including the one matching NFS vnode.  (The example output
        has been shortened for clarity.)

        # kdbx -k /vmunix
        (kdbx) vnode -u 1939
        ADDR_VNODE  V_TYPE  V_TAG USECNT V_MOUNT    
        =========== ====== ====== ====== ===========
        k0x0589d680  VDIR VT_MSFS     1  k0x013c3800  
        k0x0afeeb40  VCHR VT_MSFS     2  k0x013c3800  
        k0x096a8d80  VREG VT_MSFS     1  k0x013c3800  
        k0x0ec8ed80  VDIR VT_MSFS     1  k0x013c3800  
        k0x077f3200  VCHR VT_MSFS     2  k0x013c3800  
        k0x09374900  VREG VT_MSFS     1  k0x013c3800 
          ...
        k0x0ce6afc0  VDIR VT_MSFS     1  k0x0fa70600  
        Subcount = 394
        k0x077f2fc0  VDIR  VT_NFS     6  k0x0f217980  
        Subcount = 1
        Total count = 395

        This problem has been fixed.  kdbx will now display only the
        matching vnodes when either the '-u <uid>' or '-g <gid>' options
        are used with the 'vnode' extension.


PROBLEM: (83804, 87519) (PATCH ID: OSF520-1093)
********
Enhanced KDBX debugging features to include a -A flag for 'route' and 
to keep 'inpcb' from truncating port numbers