Class and function hooks
-classAndFunctionFile
Points to a file specifying the class and function to be hooked for the test.
If the filename contains spaces, the filename should be quoted.
The settings dialog Class and Function Filter tab provides options for creating a ready made class and function hook file by using the Export... button on the dialog.
Examples:
-classAndFunctionFile c:\settings\testMacroClassAndMethods.pvxc
-classAndFunctionFile "c:\reg tests settings\testMacroClassAndMethods.pvxc"
The first line of text in the DLL hooks file is one of the following:
•Rule:DoNotHookSpecificClasses  DLLs marked as enabled will not be hooked. All other DLLs will be hooked •Rule:HookSpecificClasses DLLs marked as enabled will be hooked. All other DLLs will not be hooked •Rule:HookAllClasses All DLLs will be hooked regardless of the settings in the list
Capitalization is important.
The remaining lines list one class and method per line.
Class and method are separated by :: or omit the method name if all methods in the class are wanted..
To name a method and no class, use :: to prefix the method.
Example:
Two methods in the pageMemoryUsageTracker class should be hooked, along with all methods in the class rightMenuAnalysis, and all methods and functions named resizeData.
Rule:HookSpecificClasses
pagedMemoryUsageTracker::setPage
pagedMemoryUsageTracker::reset
resizeData
rightMenuAnalysis::
Example:
Two methods in the pageMemoryUsageTracker class are not to be hooked.
Rule:DoNotHookSpecificClasses
pagedMemoryUsageTracker::setPage
pagedMemoryUsageTracker::reset
Example:
All classes and methods will be hooked.
Rule:HookAllClasses
The file can be ANSI or UNICODE text and paths with spaces do not need quotes.
|
Source file hooks
-sourceFileFilterHookFile
Points to a file specifying the source files to be hooked for the test.
If the filename contains spaces, the filename should be quoted.
The settings dialog Hooked Source Files tab provides options for creating a ready made source file filter hook file by using the Export... button on the dialog.
Examples:
-sourceFileFilterHookFile c:\settings\testMacroFiles.pvxft
-sourceFileFilterHookFile "c:\reg tests settings\testMacroFiles.pvxft"
The first line of text in the DLL hooks file is one of the following:
•Rule:DoNotHook Source files that follow will not be hooked. All other files will be hooked •Rule:DoHook Source files that follow will be hooked. All other files will not be hooked
Capitalization is important.
The remaining lines list one source file (or source directory) per line.
The file is named with a path or without a path, i.e. the same way that Performance Validator discovers the path.
Example:
Most files are listed with a full path but constituent files of MFC might be listed without a path.
Rule:DoNotHook
"C:\Program Files\Software Verification\C++ Performance Validator\examples\nativeExample\nativeExample.cpp"
appmodule.cpp
Example:
Using paths with and without spaces:
Rule:DoHook
"C:\Program Files\Software Verification\C++ Performance Validator\examples\nativeExample"
Rule:DoHook
E:\OM\C\PerformanceValidator\examples\nativeExample
Example:
Using environment variables.
Rule:DoHook
%ENV_VAR%\examples\nativeExample
Using wildcards.
Rule:DoHook
c:\test\*\nativeExample
The file can be ANSI or UNICODE text and paths with spaces do not need quotes.
|
Win32 API hooks
-win32API
Specifies the type of Win32 API data collection that you want.
•None No Win32 API hooking
•All Hook Win32 API functions in all DLLs
•NonOS Hook Win32 API functions in non operating system DLLs
•NonMS Hook Win32 API functions in non Microsoft DLLs
•DebugOnly Hook Win32 API functions only in DLLs that have debug information
•DebugOnlyNonMS Hook Win32 API functions only in non Microsoft DLLs that have debug information
Examples:
-win32API None
-win32API All
-win32API NonOS
-win32API NonMS
-win32API DebugOnly
-win32API DebugOnlyNonMS
