BIND 10 #2706: describe how to run scan-build (clang static analyzer)
BIND 10 Development
do-not-reply at isc.org
Wed Jun 19 22:02:52 UTC 2013
#2706: describe how to run scan-build (clang static analyzer)
-------------------------------------+-------------------------------------
Reporter: jinmei | Owner:
Type: task | Status: new
Priority: medium | Milestone: New
Component: | Tasks
documentation | Resolution:
Keywords: | CVSS Scoring:
Sensitive: 0 | Defect Severity: N/A
Sub-Project: Core | Feature Depending on Ticket:
Estimated Difficulty: 2 | Add Hours to Ticket: 0
Total Hours: 0 | Internal?: 0
-------------------------------------+-------------------------------------
Comment (by jreed):
My automated steps are like:
{{{
scan-build --keep-going -v -o ${WORKDIR}/build/scan-build make
if [ -d "${WORKDIR}/build/scan-build" ]; then
# make it error if there are bug reports to examine
exit 1
fi
}}}
If using a make target, do we want to keep the same --keep-going and -v
options?
The make target would then spawn make.
Do we want the make target to report if there are bug reports to examine?
I don't think I want to make configure detect this scan-build, but just
have a make target.
I started some simple docs about it at
http://bind10.isc.org/wiki/ClangStaticAnalyzer
--- feel free to improve it.
--
Ticket URL: <http://bind10.isc.org/ticket/2706#comment:2>
BIND 10 Development <http://bind10.isc.org>
BIND 10 Development
More information about the bind10-tickets
mailing list