Related Products: BVMS, application crash, memory dump
This article lists the scenarios in which technical support normally request dump file from a BVMS system. It contains general guidelines how to create a dump file for BVMS system and provides links to more concrete articles, that correspond to particular issues and exact steps to create a dump.
BVMS dumps are needed to troubleshoot the following types of issues:
Recommended tool to create BVMS dumps.
The recommended tool is Procdump. It is a command line tool which must be started from the command shell. Development provides couple of .bat files that start Procdump with predefined parameters and cover the most common dump creation cases. The tool as well as the set of .bat files are attached to this article: BVMS_DumpTools_V2.zip
The batch file names follow a naming guideline: <Executable>_<Dump use case> , where <Executable> is one of:
and <Dump use case> is one of
There are 3 possible error scenarios and corresponding dump creation methods:
Dump creation for reproducible crashes that trigger Windows Error Reporting
Note: attached you can find a configured example for this scenario and application Operator Client - BVMS_OC_dump_onException.zip
Dump creation for reproducible memory or handle leaks
Dump creation for crashes/hangs/freezes that are hard to reproduce
To deactivate the restarting option for Operator Client / Configuration Client: edit ..\Bosch\VMS\bin\ConfigClient.exe.config or ..\Bosch\VMS\bin\OperatorClient.exe.config.
Run the affected application/service (Operator Client, Configuration Client or Management Server Service)
As soon as the issue appears, check whether the dump was created.
Provide support with
the resulting .dmp file
description of the steps to reproduce the crash
Note: attached you can find a configured example for this scenario and application Operator Client - BVMS_OC_dump_Just-In-Time-Debuger.zip