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
dbgSaveMemoryDump (Function)
In French: dbgSauveDumpMémoire
Saves a dump of the memory used by the application. A dump of the memory used by the application corresponds to a detailed description of elements in memory as well as the memory consumed by these elements.
Unlike the debugging dump, the memory dump cannot be used to see the content of variables but only the memory footprint.
You also have the ability to create a memory dump by pressing [CTRL] + [Pause] at any time
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
// Saves the memory dump in the current runtime audit
dbgSaveMemoryDump()
Syntax

Saving the memory dump in the current dynamic audit

dbgSaveMemoryDump()
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 memory dump in a file or in interactive mode Hide the details

dbgSaveMemoryDump(<Name of Dump File>)
<Name of Dump File>: Character string (with quotes)
  • "?": starts the backup in interactive mode.
    If the dynamic audit is enabled, the memory dump is saved in the dynamic audit file.
    If the dynamic audit is disabled, a file picker allows the user to select the name of the file where the memory dump will be saved.
    In both cases, a confirmation message is displayed at the end of the operation.
  • 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\MyApi_20161023_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:
dbgSaveMemortDump("[%UserDataDir%][%exeName%]_[%Date%]_[%Time%]")
becomes
dbgSaveMemortDump(-%"[%UserDataDir%][%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:
dbgSaveMemortDump("[%UserDataDir%][%exeName%]_[%Date%]_[%Time%]")
becomes
dbgSaveMemortDump(-%"[%UserDataDir%][%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:
dbgSaveMemortDump("[%UserDataDir%][%exeName%]_[%Date%]_[%Time%]")
becomes
dbgSaveMemortDump(-%"[%UserDataDir%][%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