Public bug reported: TeamViewer is unstable and exits with a coredump on Jammy. When trying to analyze the core file using GDB 12 (debuginfod client enabled), after downloading symbols for libGL.so.1 GDB throws an internal error sect_index_text.
Affected GDB version Ubuntu 12.1-0ubuntu1~22.04, TeamViewer version is 15.45.3. Sorry that I cannot provide core file (it contain my account info), but you can try to reproduce yourself on a Jammy system. Backtrace: $ gdb -e /opt/teamviewer/tv_bin/TeamViewer -c /path/to/corefile Downloading 0.21 MB separate debug info for /lib/x86_64-linux-gnu/libGL.so.1 /build/gdb-ZgDh0V/gdb-12.1/gdb/objfiles.h:462: internal-error: sect_index_text not initialized A problem internal to GDB has been detected, further debugging may prove unreliable. ----- Backtrace ----- 0x564b9ca36077 ??? 0x564b9cd9aa64 ??? 0x564b9cd9aca0 ??? 0x564b9ceea0e4 ??? 0x564b9caf26a7 ??? 0x564b9cb265cd ??? 0x564b9cb26df1 ??? 0x564b9cd1202a ??? 0x564b9cd18c2a ??? 0x564b9ccee154 ??? 0x564b9ccefabb ??? 0x564b9cb9234b ??? 0x564b9caa53de ??? 0x564b9cbf59f5 ??? 0x564b9cbf7415 ??? 0x564b9cbf804e ??? 0x564b9c98e15f ??? 0x7fa884b60d8f __libc_start_call_main ../sysdeps/nptl/libc_start_call_main.h:58 0x7fa884b60e3f __libc_start_main_impl ../csu/libc-start.c:392 0x564b9c993bf4 ??? 0xffffffffffffffff ??? --------------------- /build/gdb-ZgDh0V/gdb-12.1/gdb/objfiles.h:462: internal-error: sect_index_text not initialized Repeated for several times, sometimes GDB just throws an internal error after downloading debuginfo for something else, but the error message is the same. Tried to generate a more complete backtrace, no good. There isn't a debuginfo package for this particular GDB version! Help wanted on generating backtraces for GDB. ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: gdb 12.1-0ubuntu1~22.04 Uname: Linux 6.1.52-x64v4-xanmod1 x86_64 NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair ApportVersion: 2.20.11-0ubuntu82.5 Architecture: amd64 CasperMD5CheckResult: unknown CurrentDesktop: ubuntu:GNOME Date: Sun Sep 10 06:08:58 2023 SourcePackage: gdb UpgradeStatus: No upgrade log present (probably fresh install) mtime.conffile..etc.logrotate.d.apport: 2023-09-06T01:56:55.105957 ** Affects: gdb (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 devel jammy -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to gdb in Ubuntu. https://bugs.launchpad.net/bugs/2035009 Title: gdb internal error sect_index_text not initialized when examining teamviewer Status in gdb package in Ubuntu: New Bug description: TeamViewer is unstable and exits with a coredump on Jammy. When trying to analyze the core file using GDB 12 (debuginfod client enabled), after downloading symbols for libGL.so.1 GDB throws an internal error sect_index_text. Affected GDB version Ubuntu 12.1-0ubuntu1~22.04, TeamViewer version is 15.45.3. Sorry that I cannot provide core file (it contain my account info), but you can try to reproduce yourself on a Jammy system. Backtrace: $ gdb -e /opt/teamviewer/tv_bin/TeamViewer -c /path/to/corefile Downloading 0.21 MB separate debug info for /lib/x86_64-linux-gnu/libGL.so.1 /build/gdb-ZgDh0V/gdb-12.1/gdb/objfiles.h:462: internal-error: sect_index_text not initialized A problem internal to GDB has been detected, further debugging may prove unreliable. ----- Backtrace ----- 0x564b9ca36077 ??? 0x564b9cd9aa64 ??? 0x564b9cd9aca0 ??? 0x564b9ceea0e4 ??? 0x564b9caf26a7 ??? 0x564b9cb265cd ??? 0x564b9cb26df1 ??? 0x564b9cd1202a ??? 0x564b9cd18c2a ??? 0x564b9ccee154 ??? 0x564b9ccefabb ??? 0x564b9cb9234b ??? 0x564b9caa53de ??? 0x564b9cbf59f5 ??? 0x564b9cbf7415 ??? 0x564b9cbf804e ??? 0x564b9c98e15f ??? 0x7fa884b60d8f __libc_start_call_main ../sysdeps/nptl/libc_start_call_main.h:58 0x7fa884b60e3f __libc_start_main_impl ../csu/libc-start.c:392 0x564b9c993bf4 ??? 0xffffffffffffffff ??? --------------------- /build/gdb-ZgDh0V/gdb-12.1/gdb/objfiles.h:462: internal-error: sect_index_text not initialized Repeated for several times, sometimes GDB just throws an internal error after downloading debuginfo for something else, but the error message is the same. Tried to generate a more complete backtrace, no good. There isn't a debuginfo package for this particular GDB version! Help wanted on generating backtraces for GDB. ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: gdb 12.1-0ubuntu1~22.04 Uname: Linux 6.1.52-x64v4-xanmod1 x86_64 NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair ApportVersion: 2.20.11-0ubuntu82.5 Architecture: amd64 CasperMD5CheckResult: unknown CurrentDesktop: ubuntu:GNOME Date: Sun Sep 10 06:08:58 2023 SourcePackage: gdb UpgradeStatus: No upgrade log present (probably fresh install) mtime.conffile..etc.logrotate.d.apport: 2023-09-06T01:56:55.105957 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gdb/+bug/2035009/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp