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 |
A call to a method that should not be used in production code.
For example, calls to System.exit() should not be used in production code, as they would disrupt the availability of your service.
Some operations should not be performed in production code, since they have no effect or have unpredictable effects, or since they might compromise the availability or security of your system.
| Class Name | Debug Call (Java) | |||||||||
|---|---|---|---|---|---|---|---|---|---|---|
| Significance | reliability | |||||||||
| Mnemonic | JAVA.DEBUG.CALL | |||||||||
| Categories |
|
|||||||||
| Availability | Available for Java only. |
|||||||||
| Enabling | Checks for this warning class are enabled by
default. To disable them, add the following WARNING_FILTER rule to the
project configuration file.
WARNING_FILTER += discard class="Debug Call (Java)" |
Japanese (ja)
import com.juliasoft.julia.extraction.EntryPoint;
public class InadequateCalls {
public @EntryPoint void check(int k) {
if (k <= 0)
System.exit(-1); // Debug Call (Java) warning issued here
else
System.out.println(k); // Debug Warning (Java) warning issued here
}
}
In this example, the programmer should signal the unusual situation in other ways, for instance by throwing an exception or by showing a dialog to the user.
Verify if the operation is adequate for production code. Remove it or transform it if that is not the case.
The following configuration file parameters affect checks for this warning class.