Add CSV option as a documented example
Signed-off-by: David A. Wheeler <dwheeler@dwheeler.com>
This commit is contained in:
parent
5ad5a17034
commit
41ccb9c0ef
13
flawfinder.1
13
flawfinder.1
|
@ -588,12 +588,21 @@ inputs appropriately).
|
||||||
Examine all the C/C++ files in the directory mydir and its subdirectories,
|
Examine all the C/C++ files in the directory mydir and its subdirectories,
|
||||||
including even the hits marked for ignoring in the code comments.
|
including even the hits marked for ignoring in the code comments.
|
||||||
|
|
||||||
|
.TP
|
||||||
|
.B "flawfinder \-\-csv ."
|
||||||
|
Examine the current directory down (recursively), and report all
|
||||||
|
hits in CSV format.
|
||||||
|
This is the recommended form if you want to further process
|
||||||
|
flawfinder output using other tools
|
||||||
|
(such as data correlation tools).
|
||||||
|
|
||||||
.TP
|
.TP
|
||||||
.B "flawfinder \-QD mydir"
|
.B "flawfinder \-QD mydir"
|
||||||
Examine mydir and report only the actual results
|
Examine mydir and report only the actual results
|
||||||
(removing the header and footer of the output).
|
(removing the header and footer of the output).
|
||||||
This form is useful
|
This form may be useful
|
||||||
if the output will be piped into other tools for further analysis.
|
if the output will be piped into other tools for further analysis,
|
||||||
|
though CSV format is probably the better choice in that case.
|
||||||
The \-C (\-\-columns) and \-S (\-\-singleline)
|
The \-C (\-\-columns) and \-S (\-\-singleline)
|
||||||
options can also be useful if you're piping the data
|
options can also be useful if you're piping the data
|
||||||
into other tools.
|
into other tools.
|
||||||
|
|
Loading…
Reference in New Issue