/usr/bin/gdb:6:dump_core:internal_vproblem:internal_verror:internal_error_loc:objfile::text_section_offset

[errors.ubuntu.com bug bridge]

The Ubuntu Error Tracker has been receiving reports about a problem regarding gdb. This problem was most recently seen with package version 14.0.50.20230907-0ubuntu1, the problem page at https://errors.ubuntu.com/problem/e052ff0ad61743594bf64a85ca1e18b6e353025d contains more details, including versions of packages affected, stacktrace or traceback, and individual crash reports.
If you do not have access to the Ubuntu Error Tracker and are a software developer, you can request it at http://forms.canonical.com/reports/.

[Benjamin Drung (bdrung)]

#3 report for foundations-bugs on mantic (373 reports in the past month)

[Benjamin Drung (bdrung)]

Looking at the crash reports (e.g. https://errors.ubuntu.com/oops/cac73123-849b-11ee-9b95-fa163ec44ecd) the ProcCmdline look similar:

/usr/bin/gdb --ex file\ "/opt/teamviewer/tv_bin/TeamViewer" --ex core-file\ /tmp/apport_core_b5i0g31o --batch --ex set\ backtrace\ limit\ 2000 -iex set\ debuginfod\ enable\ off --ex p\ -99 --ex info\ registers --ex p\ -99 --ex x/16i\ $pc --ex p\ -99 --ex bt\ full --ex p\ -99 --ex thread\ apply\ all\ bt\ full --ex p\ -99 --ex print\ __abort_msg->msg --ex p\ -99 --ex print\ __glib_assert_msg --ex p\ -99 --ex print\ (char*)\ __nih_abort_msg --ex p\ -99

So we could try to reproduce crashing with running gdb on TeamViewer.

[Mate Kukri (mkukri)]

I cannot re-produce this unfortunately. If someone manages to and could describe the conditions that lead to this and/or attach a core file, it could perhaps move forward.

[Benjamin Drung (bdrung)]

Can you document in this ticket what you tried?

[Mate Kukri (mkukri)]

I couldn't reproduce the TeamViewer crash in the first place.

I've also tried running TeamViewer under gdb, both work fine for me.

[Simon Chopin (schopin)]

How about directly sending a SIGSEGV or a SIGABRT to a working
teamviewer process using kill(1) ? That's what I usually do when I test
apport crash reporting code, this might trigger the issue.