The stack traces facility collects diagnostics information upon server failures. In general, solidDB® Support and development teams use the stack traces facility for troubleshooting. You can also generate stack traces to gain information about a problem that you are investigating, but its use is rather limited without knowledge of the solidDB® source code.
About this task
The stack traces facility is controlled with the Srv.StackTraceEnabled parameter. When set to “yes” (default), the stack trace information is output to ssstacktrace-<process_id>-<thread_id>.out file in the solidDB® working directory.
The following signals invoke the stack traces output automatically:
▪SIGSEGV
▪SIGILL
▪SIGBUS
▪SIGTRAP
▪SIGSYS
▪SIGEMT
The stack traces information is produced only about the thread that received the signal.
Additionally, you can generate the stack traces information for all currently running threads by sending the server the SIGUSR1 signal.
Note The stack traces facility is not supported on Windows operating systems.
Procedure
▪To enable or disable the stack traces facility, set the Srv.StackTraceEnabled parameter to “yes” or “no”.
▪To output the stack trace information manually without shutting down the server, send the server the SIGUSR1 signal.
For example, use the following command in Linux environments: