Trouble Shooting

Below are some common problems you may encounter when building and running MBAT:

1. SVN error: org.tigris.subversion.javahl.ClientException
   • Need to use the SVNKit client for SVN, see SVN Configuration
2. After checking out or updating the source code, you get compiler errors.
   • Due to the automated build system, some of the projects may be out of sync. Simply rebuild by cleaning all: Project > Clean..., see build instructions.
3. "Unbound classpath variable" compiler error.
   • Define the missing classpath variable, see classpath variables.
4. "unknown plug-in ID" runtime error from JPF.
   • The JPF library can not find the plugins, see configuring the working directory.
5. missing projects in the Eclipse SVN list.
   • Eclipse caches the repository list so you need to explicitly tell Eclipse to refresh
     • New > Other... > Checkout Projects from SVN > Select Folder Dialog Box: Right-click on the repository folder and select "Refresh"
6. out of memory errors.
   • increase the heap size in Eclipse:
     • "Open Run Dialog/Run Configurations". Select the Java Application you want to run. Under the "Arguments" tab, in the "VM arguments", add "-Xmx800m".
     • Performance will vary depending on your available physical memory so adjust this variable accordingly. For more details, see the documentation for "java" at http://java.sun.com/javase/6/docs/technotes/tools/index.html, under the Basic Tools section.
7. Eclipse error: "XML format error in '.classpath' file of project P: Bad format".
   • Eclipse may report this false error on startup or update from SVN. Details can be found at Eclipse bug-tracking site (Bug 150575). A couple quick of workarounds:
     • In the Navigator View (Window > Show View > Navigator), select the offending .classpath file, right click and then select Replace With > Latest from Repository.
     • If replacing from the repository doesn't work, copy the .classpath to a separate directory, delete it from Eclipse and then copy it back. If you then refresh the parent package, Eclipse should be read the file correctly.
8. Error while installing MBAT: "You need atleast a 1.6 Java Virtual Machine to install MBAT 3.0.1".
   • MBAT 3.0.1 requires JRE1.6 installed on the machine. The above message is displayed if the current version of JVM is not 1.6. On Macintosh OS-X, the system by default uses JVM1.5. We need to change the settings so that OS-X will use JVM 1.6 instead. Use following steps to change the default JVM version being used by OS-X:
     • Navigate to Applications > Utilities > Java > Java Preferences
     • Double click on the Java Preferences icon. In the "General" tab, all available Java versions are shown. Modify the Java application versions and Java applet versions order by moving Java SE 6 to the top.
     • If Java SE 6 option is not being displayed in this tab, then you need to install JDK 1.6.
9. Java Virtual Machine running out of memory
   • Win32: add command line arguments to MBAT 3.0.1.exe to specify VM parameters with the syntax -J[VM parameter] (e.g. -J-Xmx800m). Navigate to Start > Control Panel > Java. Click on the Java tab in the Java control panel. Click on "View" button. In the "Runtime Parameters" column, double click and enter "-Xmx800m". Click on "Ok" and "Apply" buttons. This will increase the maximum heap size that can be used by the JVM.
   • Unix: use the INSTALL4J_ADD_VM_PARAMS environment variables to add VM parameters to the launcher.
   • Mac OSX, edit the /Applications/MBAT 3.0.1.app/Contents/Info.plist file to change the VM parameters:

Support

If you need any other support, see the MBAT forums and post a brief description of your problem and platform configuration to the appropriate subforum.

Diagnostics

If Eclipse is having problems loading JAR or native libraries, you can try the following to view diagnostic information:

• To view the java system properties (ie: classpath, library path, etc)
  • If mbat compiles and runs:
    • Run mbat. Select Help > About. Select the System tab. Java system properties are listed under the "System Property" table (you may need to adjust the column width to see the entire path or resize the window).
  • If mbat does not run: [TODO]

• To view the full path of each JAR library loaded:
  • In Eclipse, open Run Dialog: Right-click project > Run as > Open Run Dialog... or in the toolbar, select the dropdown menu next to the Run As shortcut > Open Run Dialog....
  • Select the "Arguments" tab. Under the "VM arguments:" section, add -verbose:class.
  • When you run the application, you should see the full paths printed to the console as the JAR libraries are loaded.

• To view the full path of each native library loaded:
  • In Eclipse, open Run Dialog: Right-click project > Run as > Open Run Dialog... or in the toolbar, select the dropdown menu next to the Run As shortcut > Open Run Dialog....
  • Select the "Environment" tab. Add a new variable:
    • [Mac OSX]: set DYLD_PRINT_LIBRARIES to true
    • [Linux]: TODO
    • [Win32]: TODO
  • When you run the application, you should see the full paths printed to the console as the native libraries are loaded.