Start here

Home
About Klocwork
What's new
Fixed issues
Release notes
Installation

Reference

C/C++ checkers
Java checkers
C# checkers
MISRA C 2004 checkers
MISRA C++ 2008 checkers
MISRA C 2012 checkers
MISRA C 2012 checkers with Amendment 1
Commands
Metrics
Troubleshooting
Reference

Product components

C/C++ Integration build analysis
Java Integration build analysis
Desktop analysis
Refactoring
Klocwork Static Code Analysis
Klocwork Code Review
Structure101
Tuning
Custom checkers

Coding environments

Visual Studio
Eclipse for C/C++
Eclipse for Java
IntelliJ IDEA
Other

Administration

Project configuration
Build configuration
Administration
Analysis performance
Server performance
Security/permissions
Licensing
Klocwork Static Code Analysis Web API
Klocwork Code Review Web API

Community

View help online
Visit RogueWave.com
Klocwork Support
Rogue Wave Videos

Legal

Legal information

UMC.SYSERR

The "UMC Unwanted method calls" group of errors relates to methods such as System.exit() and System.gc() that might be unwanted. Debug print, such as System.out.println() and System.err.println(), might be unwanted as well. A UMC.SYSERR warning appears if there is a call to a print method of the System.err stream.

Vulnerability and risk

In a mature application, this call should be limited to one logging module and functional console output; otherwise it causes misused diagnostics, which should be fixed.

Mitigation and prevention

Replace calls that print to syserr with calls to the Logger module. Replace calls that print to stdout either with calls to the Logger or with calls to specific methods, for example printRawToUser().

Example 1

9      public int internalCalculateSum(int x, int y) {
10         if (x < 0 || y < 0) {
11             System.err.println("XXX: got strange arguments!");
12         }
13         return x + y;
14     }

UMC.SYSERR is reported for line 11: Debug print using System.err method calls is unwanted.