The following options may help with using and debugging the command line driven automated regression testing.

 

 

Command line help

 

-help

-?

 

Command line help is printed on the standard output.

 

 

Debugging command driven testing

 

If you're having problems with using the command line, check the following, try displaying error messages using the option below, and look at the exit return codes.

.

•separate command line arguments with spaces
 

•all command line options that include spaces need to have quotes around them
 

•some arguments are only useful in conjunction with others - check notes against each option
 

•some arguments are incompatible with others - check notes against each option

 

-showErrorsWithMessageBox

 

Forces errors to be displayed using a message box when running from the command line.

 

This can be very useful when debugging a command line that does not appear to work correctly.

 

 

Exit return codes

 

Memory Validator returns the following status codes when running from the command line.

 

•0   All ok

•-1   Unknown error. An unexpected error occurred starting the runtime

•-2   Application started ok. You should not see this code returned

•-3   Application failed to start. E.g. runtime not present, not an executable or injection dll not present,

•-4   Target application is not an application

•-5   Don't know what format the executable is, cannot process it

•-6   Not a 32 bit application

•-7   Not a 64 bit application

•-8   Using incorrect MSVCR(8|9).DLL that links to CoreDLL.dll (incorrect DLL is from WinCE)

•-9   Win16 app cannot start these because we can't inject into them

•-10 Win32 app - not used

•-11 Win64 app - not used

•-12 .Net application

•-13 User bailed out because app not linked to MSVCRT dynamically

•-14 Not found in launch history

•-15 DLL to inject was not found

•-16 Startup directory does not exist

•-17 Symbol server directory does not exist

•-18 Could not build a command line

•-19 No runtime specified, cannot execute script (or Java) (obsolete)

•-20 Java arguments are OK - not an error  (obsolete)

•-21 Java agentlib supplied that is not allowed because Java Memory Validator uses it (obsolete)

•-22 Java xrun supplied that is not allowed because Java Memory Validator uses it (obsolete)

•-23 Java cp supplied that is not allowed because Java Memory Validator uses it (obsolete)

•-24 Java classpath supplied that is not allowed because Java Memory Validator uses it (obsolete)

•-25 Firefox is already running, please close it (obsolete)

•-26 Lua runtime DLL version is not known (obsolete)

•-27 Not compatible software

•-28 InjectUsingCreateProcess, no DLL name supplied

•-29 InjectUsingCreateProcess, Unable to open PE File when inspecting DLL

•-30 InjectUsingCreateProcess, Invalid PE File when inspecting DLL

•-31 InjectUsingCreateProcess, No Kernel32 DLL

•-32 InjectUsingCreateProcess, NULL VirtualFree() from GetProcAddress

•-33 InjectUsingCreateProcess, NULL GetModuleHandleW() from GetModuleHandleW

•-34 InjectUsingCreateProcess, NULL LoadLibraryW() from LoadLibraryW

•-35 InjectUsingCreateProcess, NULL FreeLibrary() from FreeLibrary

•-36 InjectUsingCreateProcess, NULL VirtualProtect() from GetProcAddress

•-37 InjectUsingCreateProcess, NULL VirtualFree() from GetProcAddress

•-38 InjectUsingCreateProcess, unable to find DLL load address

•-39 InjectUsingCreateProcess, unable to write to remote process's memory

•-40 InjectUsingCreateProcess, unable to read remote process's memory

•-41 InjectUsingCreateProcess, unable to resume a thread

•-42 UPX compressed - cannot process such executables

•-43 Java class not found in CLASSPATH

•-44 Failed to launch the 32 bit svlGetProcAddressHelperUtil.exe

•-45 Uknown error with svlGetProcAddressHelperUtil.exe

•-46 Couldn't load specified DLL into svlGetProcAddressHelperUtil.exe

•-47 Couldn't find function in the DLL svlGetProcAddressHelperUtil.exe

•-48 Missing DLL argument svlGetProcAddressHelperUtil.exe

•-49 Missing function argument svlGetProcAddressHelperUtil.exe

•-50 Missing svlGetProcAddressHelperUtil.exe

•-51 Target process has a manifest that requires elevation

•-52 svlInjectIntoProcessHelper_x64.exe not found

•-53 svlInjectIntoProcessHelper_x64.exe failed to start

•-54 svlInjectIntoProcessHelper_x64.exe failed to return error code

•-55 getImageBase() worked ok

•-56 ReadFile() failed in getImageBase()

•-57 NULL pointer when trying to allocate memory

•-58 CreateFile() failed in getImageBase()

•-59 ReadProcessMemory() failed in getImageBase()

•-60 VirtualQueryEx() failed in getImageBase()

•-61 Bad /appName argument in svlInjectIntoProcessHelper_x64.exe

•-62 Bad /dllName argument in svlInjectIntoProcessHelper_x64.exe

•-63 Bad /procId argument in svlInjectIntoProcessHelper_x64.exe

•-64 Failed to OpenProcess in svlInjectIntoProcessHelper_x64.exe

•-65 A DLL that the .exe depends upon cannot be found

•-66 A stdin file was specified, but Validator could not open it

•-67 A stdout file was specified, but Validator could not open it

•-68 Failed to create the child output pipe

•-69 Failed to create a duplicate of the output write handle for the std error write handle. This is necessary in case the child application closes one of its std output handles

•-70 Failed to create the child input pipe

•-71 Failed to create a duplicate output read temporary file

•-72 Failed to create a duplicate input write temporary file

•-73 User was trying to launch a service as an application that was linked to MV APIs. User cancelled when informed of this fact

•-74 Returned by Memory Validator if user performs a baseline comparison and memory leaks are detected

•-75 Shutdown and restart as 32 bit Memory Validator

•-76 Shutdown and restart as 64 bit Memory Validator

•-77 Entry point in executable is NULL.

•-78 Application is .Net Core.

•-79 Entry point is for a .Net application.

•-80 VirtualAllocEx() returned NULL

•-81 InjectUsingCreateProcess, NULL GetLastError() from GetProcAddress

 

 

Updating data after test completion

 

You can run automated tests that leave the user interface open after completion,

 

The following options are used to automatically refresh the main data tabs in Memory Validator once a test is complete.

 

-refreshMemory

-refreshObjects

-refreshHotspot

-refreshAnalysis

-refreshPages