Description of problem: Debugging with GDB is broken since 5.x as gdb hangs. Tested also on 6.0.1 (built from Rawhide's SRPM in mock) - the same issue. Version-Release number of selected component (if applicable): qt-creator-5.0.1-2.fc35 (base) qt-creator-6.0.1-1.fc35 (optional) How reproducible: Always. Steps to Reproduce: 1. Start Qt Creator. 2. Load any C++ project. 3. Set any breakpoint. 4. Start debugging. Actual results: GDB will hang. The gdb process has not responded to a command within 20 seconds. This could mean it is stuck in an endless loop or taking longer than expected to perform the operation. You can choose between waiting longer or aborting debugging. Expected results: Qt Creator should stop on breakpoint. Additional info:
Most likely dependent on system environment, as it's working here (I'm debugging Qt/C++ on a daily basis with qt-creator).
Changing "Debug" -> "Views" -> "Global debugger log" fixed this issue until the next Qt Creator start.
The issue was https://fedoraproject.org/wiki/Debuginfod gdb starts working only after the debuginfod client download ~1.2 GiB of files. Can be easily reproduced. Remove all caches from ~/.cache/debuginfod* and start debugging in Qt Creator. It will hang until download complete.
Workaround: echo "set debuginfod enabled off" > ~/.gdbinit
This needs to be reassigned to a more relevant component, I can't see what qt-creator can do about it.
Changing component to gdb. Btw, workaround doesn't work with Qt Creator.
This issue should be fixed in gdb-11.1-6.fc35.x86_64. Debuginfod will not run by default when input is not coming from a terminal. Additionally 'echo "set debuginfod enabled off" > ~/.gdbinit' will now disable debuginfod. If you do wish to enable debuginfod in this case, 'echo "set debuginfod enabled on" > ~/.gdbinit' will do the trick.