Here you will find answers to frequently asked questions about the ISA Dialog Manager.
If your question is not listed, contact us!
Support / Hotline / Documentation
Monday to Friday, 9am to 4pm.
A precise problem description (what, when, how, where). Include: IDM version, platform/toolkit, window manager, and environment components.
Sample code to reproduce the error. A trace file of the process. Screenshots and videos demonstrating the error.
Troubleshooting / Tracing / Degbugging
The biggest challenge in error analysis is often locating the error. The IDM offers several options for this:
If an error can be reproduced, it is helpful to generate a trace file (ideally a complete one). This usually makes it easier to pinpoint the cause of the error.
- If the problem/crash occurs in your own application, you should consult debuggers and other components.
- In addition to the trace file, we may provide dumpstate and debugger for IDM diagnostics.
If you have not found a solution to your problem, please contact our support.
- Categorize the error (crash type/location, IDM/own application/environment, …).
- Send us a trace file
- A small example dialog that can be used to reproduce the problem is also helpful.
A trace file logs the application's execution. It can be created in the following ways:
- About the environment variable IDM_TRACEFILE
- About the parameter -IDMtracefile <Dateiname.trc> when starting the application
The start parameter overrides the environment variable.
The trace file can be configured in various ways (see the documentation chapter Start Options). Please note that a truncated trace file may not contain all the necessary information.
Über die Option -IDMtracetime (s. Dokumentation) oder den Profiler im Debugger können solche Stellen im Code ausfindig gemacht werden.
