Description of problem: I made an attempt at debugging a pdflatex crash (bug 2042421), but was stymied by a gdb internal error. I ran "gdb /usr/bin/pdflatex" and gave permission to download debuginfo. This is the tail of the GDB output: Downloading 0.01 MB separate debug info for /lib64/libbrotlicommon.so.1 Downloading -0.00 MB separate debug info for /lib64/liblzma.so.5 Downloading -0.00 MB separate debug info for /lib64/libpcre.so.1 Downloading -0.00 MB separate debug info for /builddir/.cache/debuginfod_client/37f6a27ef468c151ebdef9221635598885599a53/debuginfo ../../gdb/objfiles.h:510: 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) n This is a bug, please report it. For instructions, see: <https://www.gnu.org/software/gdb/bugs/>. ../../gdb/objfiles.h:510: 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) n Command aborted. Version-Release number of selected component (if applicable): gdb-11.1-9.fc36.x86_64 How reproducible: Always Steps to Reproduce: 1. Install texlive-latex on an x86_64 Rawhide machine 2. Invoke "gdb /usr/bin/pdflatex". 3. Invoke "run <some LaTeX file>". 4. Give GDB permission to download debuginfo. Actual results: GDB hits an internal error ... due to corrupt debuginfo downloads? GDB also reports downloading negative 0 bytes for many of the debuginfo downloads. Expected results: GDB does not hit an internal error. Additional info:
I removed ~/.cache/debuginfod_client and tried again. This time I did NOT give permission to download debuginfo. The same internal error was encountered.
The recent gdb-12.0 inclusion into rawhide packages includes a libgcc_s which lacks a .data section. Apparently, up 'til now, certain code within GDB requires a .data section to be present in executables and shared libraries. I have posted a upstream patch which fixes this problem. See: https://sourceware.org/pipermail/gdb-patches/2022-January/185430.html Once this patch makes it into upstream sources, we'll backport it to F35 and rawhide.
This bug is breaking our OpenJDK builds in Fedora rawhide which routinely check whether or not backtraces can be gathered from OpenJDK builds (bug 2041970). We had to disable this check for the time being :-/
Scratch build for those who need a working gdb on rawhide: https://koji.fedoraproject.org/koji/taskinfo?taskID=82076745
Should be fixed in gdb-11.1-12.fc36.x86_64. HOWEVER, testing shows that there are still some problems. I'm looking at those now.