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.