> For the complete documentation index, see [llms.txt](https://prosbcdocs.telcobridges.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://prosbcdocs.telcobridges.com/tmedia-documentation/server-and-os-administration/how-to-extract-backtrace-from-coredump.md).

# 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:

1. Log to the primary server (ssh)
2. Type tbsetup Usually all core files goes into the application's working directory.
3. Type cd APPLICATION where:
   * APPLICATION is the application that crashes In this example, we'll suppose APPLICATION is toolpack\_engine
4. Execute command:

```
gdb -se "APPLICATION" -ex "bt full" -ex "thread apply all bt" --batch -c CORE > /tmp/backtrace.txt
```

where:

```
- APPLICATION is the application that crashes (Full path of the application)

- CORE is the core file. (core.xxxx)
```

for example:

```
gdb -se "/lib/tb/toolpack/pkg/2.8.5/bin/release/x86_64-linux64/toolpack_engine" -ex "bt full" -ex "thread apply all bt" --batch -c core.17900 > /tmp/backtrace.txt
```

In this specific example, the crash happened at:

```
 Program terminated with signal 11, Segmentation fault.<br/> #0  0x000000000043ce59 in CallBridgingSampleDisplayMenu ()<br/> #0  0x000000000043ce59 in CallBridgingSampleDisplayMenu ()<br/>No symbol table info available.
#:
```

1. Attach the file /tmp/backtrace.txt in the TBSupport Tracking System (ticket that you opened to report the problem).

### Troubleshooting

Possible Error 1:

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](https://github.com/telcobridges-main/tmedia-wiki/tree/main/reference/api/how-to-run-toolpack-application-in-gdb/README.md)


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter:

```
GET https://prosbcdocs.telcobridges.com/tmedia-documentation/server-and-os-administration/how-to-extract-backtrace-from-coredump.md?ask=<question>&goal=<endgoal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal.

The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.