Typical command line examples
The following examples demonstrate a few different scenarios in which you might want to use Memory Validator via the command line.
To run 32 bit memory validator run C:\Program Files (x86)\Software Verify\Memory Validator x86\memoryValidator.exe
To run 64 bit memory validator run C:\Program Files (x86)\Software Verify\Memory Validator x64\memoryValidator_x64.exe
Example 1 - running a session (native or .Net)
A command line to run a program in a directory, using two arguments, and save the session without showing the Memory Validator interface:
memoryValidator_x64.exe -hideUI -program c:\myProgram.exe -arg " -macro c:\macros\testMacro1.vba" -arg "secondArg" -directory c:\testbed -saveSession c:\results\testMacro1.mvm
A brief explanation of each argument:
Option
|
Argument |
Description |
-hideUI |
Don't show the user interface during the test |
|
-program |
c:\myProgram.exe |
The target program to launch |
-arg |
" -macro c:\macros\testMacro1.vba" |
An argument to the target program |
-arg |
"secondArg" |
A second argument to the program |
-directory |
c:\testbed |
The current directory for the application to work in |
-saveSession |
c:\results\testMacro1.mvm |
Where to save the session after the application finishes |
Add the following to the first example to compare against a baseline session and export the comparison results in HTML and XML format:
-baseline c:\baselines\testMacroBaseline.mvm -sessionCompareHTML c:\regression\testMacro1.html -sessionCompareXML c:\regression\testMacro1.xml
Option
|
Argument |
Description |
-baseline |
c:\baselines\testMacroBaseline |
The baseline session to compare against (loaded at startup) |
-sessionCompareHTML |
c:\regression\testMacro1.html |
Saved HTML format results of comparison |
-sessionCompareXML |
c:\regression\testMacro1.xml |
Saved XML format results of comparison |
To show the ui and leave the Memory tab open to inspect leaks after completion, omit -hideUI in the first example and add -refreshMemory
Example 2 - running a session (.Net Core, Self Contained)
This example starts a .Net Core application, showing no progress dialog whilst attaching to the process.
On completion, the resulting session is saved, and some tabs are refreshed.
The last tab refreshed is displayed, resulting in the Functions tab being the current tab.
memoryValidator_x64.exe -program "c:\myDotNetCoreApp.exe" -dotNetCoreLaunchType SelfContained -saveSession "c:\myResults\session2.mvm" -displayUI
A brief explanation of each argument:
Option
|
Argument |
Description |
-program |
"c:\myDotNetCoreApp.exe" |
The target program to launch |
-dotNetCoreLaunchType |
SelfContained |
The .Net Core program is self contained |
-saveSession |
"c:\myResults\session2.mvm" |
After the application finishes, the session should be saved in this file |
-displayUI |
Show the user interface during the performance test |
Example 3 - running a session (.Net Core, Framework Dependent)
This example starts a .Net Core application, showing no progress dialog whilst attaching to the process.
On completion, the resulting session is saved, and some tabs are refreshed.
The last tab refreshed is displayed, resulting in the Functions tab being the current tab.
memoryValidator_x64.exe -program "c:\dotNetCoreApp.dll" -dotNetCoreLaunchType FrameworkDependent -saveSession "c:\myResults\session3.mvm" -displayUI
A brief explanation of each argument:
Option
|
Argument |
Description |
-program |
"c:\dotNetCoreApp.dll" |
The target program to launch with the .Net runtime |
-dotNetCoreLaunchType |
FrameworkDependent |
The .Net Core program is framework dependent |
-saveSession |
"c:\myResults\session3.mvm" |
After the application finishes, the session should be saved in this file |
-displayUI |
Show the user interface during the performance test |
