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.2p0 | CONFIDENTIAL | CodeSecure Inc |
At any given time, you will probably be interested in only a subset of the warnings issued by CodeSonar and stored on the hub. For example, you may want to see only warnings belonging to a specific user, or only warnings in one particular file. The search facilities in CodeSonar allow you to find the warnings you are interested in.
Search functionality can always be accessed through the search widget that appears on every page in the CodeSonar GUI. The following annotated screenshot fragment shows the different parts of the search widget.
What do you want to do?
| full-text search | Find warnings whose reports contain one or more specific strings (in any field). |
|---|---|
| advanced search | Find warnings by specifying the desired contents for one or more report fields. |
| search language search | Find warnings by using the search language to precisely specify a search. |
All of these methods will list the matching warnings on a Warning Search Result Page.
This is the simplest way to search for warnings. Given one or more strings, the CodeSonar full-text search will list all warnings whose reports contain the string or strings, regardless of where in the report they occur.
So long as there is a warning with Instance ID 365, this is the most straightforward method for finding it.
Note that this search will also find any other warnings that contain the string "365", such as
Note that this search will also find any other warnings that contain all of the strings "Null", "Pointer" and "Dereference" together or separately but are not themselves Null Pointer Dereference warnings. For example, if a user had added the comment "Fix null pointer dereferences before fixing this" to the report for a Unused Code warning, that warning will be found. There are two ways to address this.
The CodeSonar advanced search allows you to specify searches more precisely than full-text search. It is useful when the search criteria are complex and when full-text search would match a broader set of warnings than is actually desired.
This process is slightly more involved than that for finding warning 365 with full-text search, but has the advantage of only finding warnings whose Instance ID is "365", and not ones where "365" occurs only in some other field.
This search will find the warning with Instance ID 365 (if any).
This search will find only Null Pointer Dereference warnings.
The search language search combines the precision of the advanced search with the simple interface of the full-text search.
This search will find the warning with Instance ID 365 (provided it exists), and only that warning.
This search has exactly the same results as the advanced search version but has the advantage that it can be executed from any screen in the CodeSonar GUI.
Related tasks
Using CodeSonar
To report problems with this documentation, please visit https://support.codesecure.com/.