PC SOFT

ONLINE HELP
FOR WINDEV, WEBDEV AND WINDEV MOBILE

Home | Sign in | English US
WINDEV
WindowsLinuxUniversal Windows 10 AppJavaReports and QueriesUser code (UMC)
WEBDEV
WindowsLinuxPHPWEBDEV - Browser code
WINDEV Mobile
AndroidAndroid Widget iPhone/iPadApple WatchUniversal Windows 10 AppWindows Mobile
Others
Stored procedures
dbgEndMemoryDiff (Function)
In French: dbgFinDiffMémoire
Saves a memory dump containing the memory resources that have been allocated and that have not been freed since the previous call to dbgStartMemoryDiff.
This debugging method is used to isolate the memory resources of an operation that should be neutral for the memory. This allows you to correct the code and to add the potential missing freeing statements (queries no longer used, global object no longer used during the rest of the execution, ...).
Versions 18 and later
Universal Windows 10 App This function is now available in Windows Store apps mode.
New in version 18
Universal Windows 10 App This function is now available in Windows Store apps mode.
Universal Windows 10 App This function is now available in Windows Store apps mode.
Versions 21 and later
Universal Windows 10 App This function is now available in Universal Windows 10 App mode.
New in version 21
Universal Windows 10 App This function is now available in Universal Windows 10 App mode.
Universal Windows 10 App This function is now available in Universal Windows 10 App mode.
Example
// Beginning of the memory diff
// before the operation that should be neutral for the memory
dbgStartMemoryDiff()

...

// Operation that should be neutral for the memory
...

// Save the memory dump
// after the operation that should be neutral for the memory
dbgEndMemoryDiff()
Syntax

Saving the difference memory dump in the current dynamic audit

dbgEndMemoryDiff()
Note: This syntax saves the memory dump in the dynamic audit file if the audit is enabled. The function has no effect if the dynamic audit is not enabled.

Saving the difference memory dump in a file Hide the details

dbgEndMemoryDiff(<Name of Dump File>)
<Name of Dump File>: Character string (with quotes)
Name of the file where the dump is saved. The name of the file can be built with the following elements:
[%ExeDir%]Directory of executable, always filled with the "\" character. This directory is equivalent to the result of fExeDir.
[%ExeName%]Executable name.
[%Date%]Start date of memory dump (YYYYMMDD format).
[%Time%]Start time of memory dump (HHMMSS format).
[%UserName%]Name of current user.
[%ComputerName%]Computer name.
Versions 18 and later
[%DataDir%]
New in version 18
[%DataDir%]
[%DataDir%]
Directory of HFSQL data files specified by the user when installing the application. This directory is equivalent to the result of fDataDir.
Versions 18 and later
[%DirUserData%]
New in version 18
[%DirUserData%]
[%DirUserData%]
Directory for the data of the current user of the current application. This directory is equivalent to the result of fDataDirUser.
If this parameter corresponds to an empty string (""):
  • The extension of the file will be ".wmem".
  • before version 180062: the name of the created file corresponds to: "[%ExeDir%][%ExeName%]_[%Date%]_[%Time%]".
    For example: "C:\MyApp\MyApp_20091023_130812.wmem".
  • from version 180062: the name of the created file corresponds to: "[%UserDataDir%][%ExeName%]_[%Date%]_[%Time%]".
    For example: "C:\Users\Doc\AppData\Roaming\WinDev Applications\MyApp\MyApp_20091023_130812.wmem".
If this parameter corresponds to an empty string (""):
  • The extension of the file will be ".wmem".
  • The name of the created file corresponds to: "[%UserDataDir%][%ExeName%]_[%Date%]_[%Time%]".
    For example: "C:\Users\Doc\AppData\Roaming\WinDev Applications\MyApp\MyApp_20091023_130812.wmem".
Versions 22 and later
Caution: If you are using the dynamic construction of strings ("Allow "[% %]" in the strings" option in the "Compilation" tab of project description), a compilation error occurs (unknown identifier). In this case, each string must be preceded by '-%'. Example:
dbgEndMemoryDiff("[%DirUserData%][%exeName%]_[%Date%]_[%Time%]")
becomes
dbgEndMemoryDiff(-%"[%DirUserData%][%ExeName%]_[%Date%]_[%Time%]")
New in version 22
Caution: If you are using the dynamic construction of strings ("Allow "[% %]" in the strings" option in the "Compilation" tab of project description), a compilation error occurs (unknown identifier). In this case, each string must be preceded by '-%'. Example:
dbgEndMemoryDiff("[%DirUserData%][%exeName%]_[%Date%]_[%Time%]")
becomes
dbgEndMemoryDiff(-%"[%DirUserData%][%ExeName%]_[%Date%]_[%Time%]")
Caution: If you are using the dynamic construction of strings ("Allow "[% %]" in the strings" option in the "Compilation" tab of project description), a compilation error occurs (unknown identifier). In this case, each string must be preceded by '-%'. Example:
dbgEndMemoryDiff("[%DirUserData%][%exeName%]_[%Date%]_[%Time%]")
becomes
dbgEndMemoryDiff(-%"[%DirUserData%][%ExeName%]_[%Date%]_[%Time%]")
Components
WINDEVWEBDEV - Server codeReports and Queries wd230vm.dll
Windows Mobile wp230vm.dll
Linux wd230vm.so
Minimum required version
  • Version 15
This page is also available for…
Comments
Click [Add] to post a comment