Summary: | GDB fails to read build ID from debug file | ||
---|---|---|---|
Product: | gdb | Reporter: | Antoine Allard <antoine.allard> |
Component: | gdb | Assignee: | Not yet assigned to anyone <unassigned> |
Status: | UNCONFIRMED --- | ||
Severity: | normal | CC: | simon.marchi |
Priority: | P2 | ||
Version: | HEAD | ||
Target Milestone: | --- | ||
Host: | Target: | ||
Build: | Last reconfirmed: |
Description
Antoine Allard
2024-06-05 09:54:22 UTC
Any insight on the possible root cause of this issue or how to debug GDB itself to understand what's wrong with my binaries would be really appreciated :) (not sure if I filled the bug report correctly as well, let me know if that's not the case) Any insight on the possible root cause of this issue or how to debug GDB itself to understand what's wrong with my binaries would be really appreciated :) (not sure if I filled the bug report correctly as well, let me know if that's not the case) I have no idea off hand for your actual problem. But to debug GDB, configure (the top-level configure in binutils-gdb) with something like: $ ./configure CFLAGS="-g3 -O0" CXXFLAGS="-g3 -O0" $ make all-gdb -j$(nproc) # the all-gdb target, in order to avoid building the other tools Then I usually cd in the gdb directory and use: $ ./gdb -nx -q --data-directory=data-directory <other args> And you can debug gdb itself by doing: $ gdb --args ./gdb -nx -q --data-directory=data-directory <other args> Debugging something like this should be relatively easy, since it's not something timing dependent. Break at the point the message is issued and work your way up to see when code paths diverge. |