How To extract backtrace from coredump
When a fault happens in toolpack, developers may need to get more useful information to fix the problem.
Getting the "Minidump"
Most Toolpack applications will generate a "minidump" when crashing. This dump provides valuable information for engineering teem for identifying the source of the problem.
Please look at the working directory of the faulty application (type "tbsetup" on the shell, then "cd [the application folder]/dumps), and then:
Download the corresponding ".dmp" file (by date/time)
Send it to support team (these files are small, can be sent by email easily)
Indicate the exact Toolpack version that the application was running (2.8.103 for example)
Running GNU Debuger (GDB)
Linux core dump will also provide useful information related to a fault in the code:
Log to the primary server (ssh)
Type tbsetup Usually all core files goes into the application's working directory.
Type cd APPLICATION where:
APPLICATION is the application that crashes In this example, we'll suppose APPLICATION is toolpack_engine
Execute command:
gdb -se "APPLICATION" -ex "bt full" -ex "thread apply all bt" --batch -c CORE > /tmp/backtrace.txtwhere:
for example:
In this specific example, the crash happened at:
Attach the file /tmp/backtrace.txt in the TBSupport Tracking System (ticket that you opened to report the problem).
Troubleshooting
Possible Error 1:
gdb -bash: gdb: command not found
This is because you did not install the gdb package. You can do: yum install gdb
Possible Error 2: warning: exec file is newer than core file. warning: no loadable sections found in added symbol-file system-supplied DSO at 0x7fffa11ec000
This is because the core dump file (CORE) was not generated by the pointed application (APPLICATION). It was generated by an older version of toolpack application. Make sure the core dump file matches the application that you gave as an argument to GDB.
If you prefer to run the application in gdb, consult this page
Last updated
Was this helpful?