The defects discovered by coverity SA including errors of STLPort, Boost, Qt libs as well, Is there any way to exclude these errors while running cov-build or cov-analyze?
Coverity SA - excluding boost, stlport errors
1.3k Views Asked by Shrikant At
1
There are 1 best solutions below
Related Questions in COVERITY-PREVENT
- Drupal access control to custom user profile page
- How to list all child pages of current parent page in drupal 7?
- MariaDB/MySQL all of a sudden crashed and won't restart
- Drupal location module shows only a portion of Gmap on node page
- How to add a select collection type select list to field collection
- Drupal7 modified user login no effect?
- Drupal AngularJS ajax simple ng-repeat update
- Drupal: Access A Field in hook_views_query_alter()
- Drupal Webform : set SCORE on each SELECT Options?
- Register new user as authenitcated user in drupal using xml-rpc
Related Questions in COVERITY
- Drupal access control to custom user profile page
- How to list all child pages of current parent page in drupal 7?
- MariaDB/MySQL all of a sudden crashed and won't restart
- Drupal location module shows only a portion of Gmap on node page
- How to add a select collection type select list to field collection
- Drupal7 modified user login no effect?
- Drupal AngularJS ajax simple ng-repeat update
- Drupal: Access A Field in hook_views_query_alter()
- Drupal Webform : set SCORE on each SELECT Options?
- Register new user as authenitcated user in drupal using xml-rpc
Trending Questions
- UIImageView Frame Doesn't Reflect Constraints
- Is it possible to use adb commands to click on a view by finding its ID?
- How to create a new web character symbol recognizable by html/javascript?
- Why isn't my CSS3 animation smooth in Google Chrome (but very smooth on other browsers)?
- Heap Gives Page Fault
- Connect ffmpeg to Visual Studio 2008
- Both Object- and ValueAnimator jumps when Duration is set above API LvL 24
- How to avoid default initialization of objects in std::vector?
- second argument of the command line arguments in a format other than char** argv or char* argv[]
- How to improve efficiency of algorithm which generates next lexicographic permutation?
- Navigating to the another actvity app getting crash in android
- How to read the particular message format in android and store in sqlite database?
- Resetting inventory status after order is cancelled
- Efficiently compute powers of X in SSE/AVX
- Insert into an external database using ajax and php : POST 500 (Internal Server Error)
Popular # Hahtags
Popular Questions
- How do I undo the most recent local commits in Git?
- How can I remove a specific item from an array in JavaScript?
- How do I delete a Git branch locally and remotely?
- Find all files containing a specific text (string) on Linux?
- How do I revert a Git repository to a previous commit?
- How do I create an HTML button that acts like a link?
- How do I check out a remote Git branch?
- How do I force "git pull" to overwrite local files?
- How do I list all files of a directory?
- How to check whether a string contains a substring in JavaScript?
- How do I redirect to another webpage?
- How can I iterate over rows in a Pandas DataFrame?
- How do I convert a String to an int in Java?
- Does Python have a string 'contains' substring method?
- How do I check if a string contains a specific word?
There are several ways to exclude these libraries.
At the highest level, you can choose to exclude them during build or analysis and then there won't be any results for them in the UI, unfortunately that also means that you will not get as complete of a view of your own errors in your own code, since analysis does inter procedural examination of various interactions.
So instead you can do something that's easier. Go ahead, analyze all of the code including all the libraries, etc. but then set up components in the UI and create permissions on the components corresponding to "third party" source such that the users can see the source code (and can navigate to it) but cannot see the defects. This allows complete information in the UI for developers triaging defects in their own code without being distracted by defects in code they don't have control over.