This will set the configuration variables for NeXtMidas and create the
Save File that will be used.
Start JProbe (in this example it is the test-coverage module of JProbe that
will be used, but the configuration, once set, should work with the other
JProbe modules). Do this by running:
$ $JPROBE/bin/jpcoverage
(Note: $JPROBE is the installation
directory of JProbe, often /opt/JProbe_Suite_5.2.0)
The first thing that comes up should be the "Welcome to JProbe Coverage"
window.
In the "Welcome to JProbe Coverage" window click the "Acquire..." button.
This will bring up the "JProbe LaunchPad" window.
(Note: Unlike the above image your image will not have "nxm" listed yet.)
In the "JProbe LaunchPad" window click the "Manage Configurations..."
button. This will bring up the "Manage J2SE Configurations" window (note:
make sure it says "J2SE" and not "J2EE").
In the "Manage J2SE Configurations" window click the "Add..." button
to add a new configuration names "nxm".
In the "Create J2SE Configuration" window enter the following (it
will be necessary to click the "..." button to edit the "Classpath"
and "Java Options" fields):
When you are done it should look similar to the following:
Click "OK" in both the "Create J2SE Configuration," "Manage J2SE
Configurations," and the "JProbe LaunchPad" windows.
In the "JProbe Coverage" window select "Session" and then "Save
Settings" to save the settings. (It is suggested that you save the
settings in your home directory in a file named
"nxm.jpl".)
In the "JProbe Coverage" window select "Session" and then "Exit" to
exit JProbe.
Note: Setting -DNONATIVE=TRUE disables using native code for
automatic conversions but makes debugging easier. Setting
-DNOEXTERNAL=TRUE prevents the shell from exiting when an OS
command is run (or a command is mistyped).
Run the JProbe application:
jpmemorydebugger
Debugs memory usage.
jpprofiler
Profiles the code.
jpcoverage
Determines which lines of code the test cases cover.
etc.
Run nmend to clean out the NeXtMidas parameters and delete
the save file.