Skip to main content

Notice: this Wiki will be going read only early in 2024 and edits will no longer be possible. Please see: https://gitlab.eclipse.org/eclipsefdn/helpdesk/-/wikis/Wiki-shutdown-plan for the plan.

Jump to: navigation, search

Linux Tools Project/Test Plans/Valgrind

Manual Valgrind Plugin Testing

  1. Install valgrind on your host system.
  2. Using a new or existing C/C++ project, right click it in the Project Explorer view and select Profile As -> Profile With Valgrind
    1. You can use these simple test projects. Import them via File->Import->General->Existing Projects into Workspace->Select archive file.
  3. The Valgrind View should appear after execution finishes, if there are any memory management errors, they will appear inside of it.
  4. For further testing, right click the project again in the Project Explorer view and select Profile As -> Profile Configurations.
  5. Choose the Valgrind run configuration just created and select the "Valgrind Options" tab.
  6. Select the "Tool to run" drop-down, memcheck and massif should be listed, select massif and click "Profile".
  7. The Valgrind View should appear after execution finishes, tabular heap allocation data should be shown in it. Also a line chart of this data should appear as the active editor.

Unit Testing

  1. Checkout all Valgrind plugin sources from Subversion
    1. Use this Project Set File
    2. See PSF for more details on Project Set Files
  2. Ensure no build errors with all Vaglrind plugins
    1. You will need dependencies such as EMF and BIRT installed; install these from the main Galileo or Helios update site
  3. Run the JUnit tests
    1. In org.eclipse.linuxtools.valgrind.memcheck.tests and org.eclipse.linuxtools.massif.tests, right click on AllTests.java and select Run As -> JUnit Plug-in Test
  4. All tests should pass

Back to the top