Exporting Memory Analysis data

You can export Memory Analysis sessions to XML files if you want to share analysis results. You can also export event data to CSV files if you want to view the data in a spreadsheet application.

Although the Memory Analysis tool produces a log (.rmat) file for every session, this file type doesn't have as much information as the XML files generated by the export feature. You can import a log into the IDE, but for the event data to include line numbers (and hence, be readable), your host needs to have copies of the application binary and any shared libraries used during the session. Conversely, the XML file format is self-contained and doesn't require any supporting files on the host.
To export Memory Analysis sesssion data:
  1. Select File > Export > QNX > Memory Analysis Data, then click Next.
    Alternatively, if the Analysis Sessions view is open, you can right-click any Memory Analysis session and choose Export Session.
  2. In the Export window, select the sessions for which you want to export data.
    In this window, the Memory Analysis sessions are listed from oldest (at the top) to newest (at the bottom), with checkboxes for selecting individual sessions. There are also Select All and Deselect All buttons.
  3. In the Output File field, specify the file for storing the data.
    You can enter an absolute host path or click Browse to choose a directory from a file selector. You must enter a file name in the selector window. The file extension is preset depending on which radio button is currently selected in Options.
  4. In the Options panel, choose the output details.
    The Export all option is selected by default and lets you export all selected sessions to a single XML file. The other four options let you export the data from a specific event type to a CSV file:
    • Export memory events — Allocation and deallocation events
    • Export runtime errors — Memory errors or leaks detected by the tool
    • Export bin events — Events related to bins, which group allocations based on byte size ranges
    • Export band events — Events related to bands, which provide preallocated memory for satisfying small allocation requests

    If you choose to export the data for an event type, you can check Generate header row to include column headers that display field names in the output file.

  5. Click Finish.
    The IDE writes the data from the selected sessions to the output file, in the format indicated by the Options panel. If you specified an existing file, the IDE asks if you want to overwrite it.
For XML files, the session data stored in them can be imported into a different IDE installation, even one of another version. For CSV files, you can view the event data in a spreadsheet application such as Excel. The Memory Analysis reference explains the CSV file contents for exported event data.