JavaScript is not currently enabled, but is required for full CodeSonar manual search and browse functionality.
If you are viewing this file in your hub's Web GUI, enable JavaScript in your browser: you will also need it for GUI functionality.
If you opened this file directly from disk, your browser may be directly suppressing JavaScript functionality: certain browsers perform this suppression on local files (but not files delivered by web servers) for security reasons.
| CodeSonar® 9.0p0 Hot Tips | CONFIDENTIAL | CodeSecure Inc |
If your development team is organized so that different users have responsibility for different parts of the system, it is useful to be able to assign groups of related warnings to a user in one big batch, rather than assigning each warning separately. This operation has two parts:
Suppose you want to assign all warnings in the directory src/ioutil to Lindsay.
CodeSonar will display a page that describes the changes you made and lists the warning reports affected.
The method described above is suitable for assigning warnings from analyses that have already been performed.
You can also instruct CodeSonar to assign all warnings from future analyses to Lindsay if they are in directory src/ioutil. To do this, you will use a WARNING_FILTER rule in the general template configuration file.
WARNING_FILTER += owner:=Lindsay path:src/ioutil WARNING_FILTER += owner:=Lindsay path:src\ioutil
For future analyses with the corresponding CodeSonar installation, Lindsay will now be established as the owner of warnings issued in src/ioutil before the warnings are submitted to the hub.