Included you will find for dmdirc:

report_build_1.xml - Klocwork xml format, out of the box settings
report_build_1_sate.xml - Your xml format, out of the box settings 

report_build_2.xml - Klocwork xml format, tuned project
report_build_2_sate.xml - Your xml format, tuned project

problems_default.pconf.xml - turns off two checkers, see reasons below
*	JD.OVER this checker detects the situations where there can be a
potential method mis-override. So it does not report actual defects, but
rather the list of places worth checking out. We assume it is not so
interesting in the context of the given project.
*	RI.IGNOREDNEW - this checker reports when the newly created
object is not assigned anywhere. In 'dmdirc' project you can see
numerous examples of such code. Those objects constructor creates a
Thread, so the object does not immediately disappear. Saying that we
would call it a bad coding style: if you create an object only for the
purpose of creating a thread one should use a factory method pattern for
better performance. But that is a subtle issue, so we decided to turn
that off.

tuning.jkb - tuning file use to tune 2 checkers, see reasons below
*	NPE.RET.UTIL: We suppressed a bunch of sources of NPE.RET.UTIL
defects, since there were the checks for the state of collections in use
which were not detected
*	SV.IL.FILE: We marked a couple of logging methods as saved ones
from the point of view of information leaks

Included for the pvm C track:

report_cxx.xml - Klocwork xml format, out of the box settings
report_cxx_sate.xml - Your xml format, out of the box settings

There is no tuning for the C track.
