Generating Stack Traces

In the event of a core dump, it is advisable to generate stack traces from the core dump and send the traces to ENOVIA Support.

See Also
Memory Pools
Memory Management
Studio Customization Toolkit Origin Tracing
  1. Generate stack traces from the core dump. This will provide information about where all running threads were in the code at the time of the crash.
  2. Examine the core file on the system that generated it.
  3. Examine the stack trace. The first thread in the stack trace output is the one that caused the crash. Normally, there is an entry that reads sighdlr and the entry just after it is the one that caused the "signal" (usually SIGSEGV) and the crash.
  4. Send the stack trace to ENOVIA Support.