- PLUGY CHECKING LIBRARY MEMORY CHECK FAILED 1.13 FULL
- PLUGY CHECKING LIBRARY MEMORY CHECK FAILED 1.13 CODE
PLUGY CHECKING LIBRARY MEMORY CHECK FAILED 1.13 FULL
When you integrate all of the modules into the full program, you are likely to encounter few new errors. That way, you deal with a smaller number of errors at a time. Write a unit test to drive each module and use runtime checking incrementally to check one module at a time. One way to avoid seeing a large number of errors at once is to use runtime checking earlier in the development cycle-as you are developing the individual modules that make up your program. You can use runtime checking by using the check command. There are some special considerations with programs not compiled with the -g option.
Runtime checking can also check programs compiled with the optimization -O flag.
It is not available on platforms running the Linux OS. Note - Runtime checking is available on platforms running the Solaris OS only.
PLUGY CHECKING LIBRARY MEMORY CHECK FAILED 1.13 CODE
Runtime checking (RTC) lets you automatically detect runtime errors, such as memory access errors and memory leak, in a native code application during the development phase.