Description of problem:

While extracting debug info for python-graph-tool, gdb crashes with an assertion failure.

Version-Release number of selected component (if applicable): gdb-13.1-3.fc39, python-graph-tool-2.49-1.fc39


How reproducible:


Steps to Reproduce:
1. fedpkg co python-graph-tool
2. cd python-graph-tool
3. fedpkg mockbuild

Actual results:

Successful build with some problems creating debug info.

extracting debug info from /builddir/build/BUILDROOT/python-graph-tool-2.49-1.fc38.x86_64/usr/lib64/python3.11/site-packages/graph_tool/util/libgraph_tool_util.so
../../gdb/dwarf2/index-write.c:1069: internal-error: assert_file_size: Assertion `file_size == expected_size' failed.
A problem internal to GDB has been detected,
further debugging may prove unreliable.
----- Backtrace -----
0x55c8fa05da30 ???
0x55c8fa4580ac ???
0x55c8fa4583ae ???
0x55c8fa6372b4 ???
0x55c8fa11cbf3 ???
0x55c8fa11dbb0 ???
0x55c8fa120e8e ???
0x55c8fa1222f4 ???
0x55c8fa096ba4 ???
0x55c8fa435545 ???
0x55c8fa26b439 ???
0x55c8fa26b521 ???
0x55c8fa26d5c8 ???
0x55c8fa26e1af ???
0x55c8f9f75d6e ???
0x7fb5b7848b49 ???
0x7fb5b7848c0a ???
0x55c8f9f7ed64 ???
0xffffffffffffffff ???
---------------------
../../gdb/dwarf2/index-write.c:1069: internal-error: assert_file_size: Assertion `file_size == expected_size' failed.
A problem internal to GDB has been detected,
further debugging may prove unreliable.
Quit this debugging session? (y or n) [answered Y; input not from terminal]

This is a bug, please report it.  For instructions, see:
<https://www.gnu.org/software/gdb/bugs/>.

/usr/bin/gdb-add-index: line 135: 24817 Aborted                 (core dumped) $GDB --batch -nx -iex 'set auto-load no' -iex 'set debuginfod enabled off' -ex "file $file" -ex "save gdb-index $dwarf5 $dir"
gdb-add-index: gdb error generating index for /builddir/build/BUILDROOT/python-graph-tool-2.49-1.fc38.x86_64/usr/lib64/python3.11/site-packages/graph_tool/inference/libgraph_tool_inference.so

Expected results:

Successful build with useful debug info.

Additional info:

The python-graph-tool package takes a lot of time and memory to compile, so it may be better to do a scratch build if not working on a workstation with plenty of RAM and CPU cores.

It’s not immediately obvious to me how to get a useful backtrace from the automatic invocation of gdb during debug info extraction, but I’m happy to do any experiments that might help if I can get a little guidance on what is needed.

It looks like the underlying problem has been around for quite a while; see bug 1773651.