6282 ONBLD man pages not pbchk clean
Reviewed by: Yuri Pankov <yuri.pankov@nexenta.com>
Reviewed by: Josef Sipek <jeffpc@josefsipek.net>

*** 17,34 ****
  .\" "
  .\" " CDDL HEADER END
  .\" "
  .\" "Copyright 2008 Sun Microsystems, Inc.  All rights reserved.
  .\" "Use is subject to license terms.
! .TH lintdump 1ONBLD "28 Mar 2008"
  .I lintdump
  \- dump the contents of one or more lint objects
  .SH SYNOPSIS
  \fBlintdump [-i] [-p 1|2|3] [-r] \fIlintobj\fP [ \fIlintobj\fP ... ]
- .LP
  .SH DESCRIPTION
- .IX "OS-Net build tools" "lintdump" "" "\fBlintdump\fP"
  .LP
  The lintdump utility dumps the contents of one or more lint
  objects.  This is chiefly useful when trying to understand the cause of
  unexpected or obtuse lint warnings (see EXAMPLES), but can also be used to
  find differences between lint objects across builds or releases, or to
--- 17,32 ----
  .\" "
  .\" " CDDL HEADER END
  .\" "
  .\" "Copyright 2008 Sun Microsystems, Inc.  All rights reserved.
  .\" "Use is subject to license terms.
! .TH LINTDUMP 1ONBLD "Mar 28, 2008"
  .I lintdump
  \- dump the contents of one or more lint objects
  .SH SYNOPSIS
  \fBlintdump [-i] [-p 1|2|3] [-r] \fIlintobj\fP [ \fIlintobj\fP ... ]
  .SH DESCRIPTION
  .LP
  The lintdump utility dumps the contents of one or more lint
  objects.  This is chiefly useful when trying to understand the cause of
  unexpected or obtuse lint warnings (see EXAMPLES), but can also be used to
  find differences between lint objects across builds or releases, or to
*** 66,76 ****
  .B -p 1|2|3
  Just output the PASS1, PASS2, or PASS3 section.
  .TP 10
  .B -r
  Output records using relative paths (see EXAMPLES).
- .LP
  .SH OUTPUT
  .LP
  The contents of each specified \fIlintobj\fP is dumped in command-line
  order.  For each \fIlintobj\fP, lintdump outputs a single line beginning
  with "LINTOBJ:" that provides its name.  For each lint module within that
--- 64,73 ----
*** 150,166 ****
  SECTION: PASS3: 130 bytes
     FILE: /home/meem/hacks/liba.c
     FILE: liba.c
           int af(void) <returns value>;
  .fi
- .LP
  .SH RECORD PROPERTIES
  .LP
  As discussed in OUTPUT, some records are displayed using an extended
  format to convey information that cannot be expressed in C.  The following
  extended information may be displayed:
- .RE
  .LP
  .B <PRINTFLIKE\fIn\fP>
  .RS 4
  Indicates to lint that argument \fIn\fP to the variable-argument function
  is a format string in printf(3C) format, which enhances lint's argument
--- 147,161 ----
*** 200,210 ****
  .LP
  .B <returns value>
  .RS 4
  Indicates to lint that the function returns a value.
  .RE
- .LP
  .SH EXAMPLES
  .LP
  One common problem is that lint does not always provide sufficient
  information to understand the reason for a type mismatch.  For instance,
  sometimes lint will confusingly report a type mismatch between
--- 195,204 ----
*** 306,316 ****
  .fi
  .LP
  Note that -r option removes spurious differences that would otherwise
  arise from different absolute paths to the same source file, and the -i
  option removes spurious differences due to ID generation inside lint.
- .LP
  .SH SEE ALSO
  .LP
  .IR lint(1),
  .IR printf(3C),
  .IR scanf(3C)
--- 300,309 ----