-
Bug
-
Resolution: Done-Errata
-
Normal
-
rhel-9.3.0.z
-
gdb-14.2-3.el9
-
None
-
None
-
1
-
rhel-sst-pt-perf-debug
-
ssg_platform_tools
-
16
-
17
-
1
-
False
-
-
No
-
Perf Debug Sprint 6
-
Unspecified Release Note Type - Unknown
-
None
When attaching to a process in a container based on its PID, GDB begins to load shared objects, but eventually runs into an internal error.
Try: dnf --enablerepo='*debug*' install /usr/lib/debug/.build-id/2b/3060a28a992246fb32e1412965c3195dc15558.debug Reading symbols from .gnu_debugdata for target:/lib64/libzstd.so.1... --Type <RET> for more, q to quit, c to continue without paging--c (No debugging symbols found in .gnu_debugdata for target:/lib64/libzstd.so.1) Reading symbols from target:/lib64/libgcc_s.so.1... Missing separate debuginfo for target:/lib64/libgcc_s.so.1 Try: dnf --enablerepo='*debug*' install /usr/lib/debug/.build-id/79/c495e864b08cd6581dda7b5836ce55a77d50cc.debug Reading symbols from .gnu_debugdata for target:/lib64/libgcc_s.so.1... (No debugging symbols found in .gnu_debugdata for target:/lib64/libgcc_s.so.1) ../../gdb/objfiles.h:530: internal-error: sect_index_data not initialized A problem internal to GDB has been detected, further debugging may prove unreliable. Quit this debugging session? (y or n) y This is a bug, please report it. For instructions, see: <https://www.gnu.org/software/gdb/bugs/>. ../../gdb/objfiles.h:530: internal-error: sect_index_data not initialized A problem internal to GDB has been detected, further debugging may prove unreliable. Create a core file of GDB? (y or n) y Aborted
Seen with gdb-10.2-11.el9.x86_64.
This does not seem to happen with all processes in that container. I see it with this one:
/usr/libexec/pcp/bin/pmnsmerge root root_jbd2 root_kvm root_linux root_mmv root_pmcd root_pmproxy root_proc root_root root_xfs root.new
I don't know what's special about it—pmnsmerge is hanging and I was trying to get a backtrace using GDB.
- links to
-
RHEA-2024:133467
gdb bug fix and enhancement update
