| Summary: | Make the "build ID" method of having separate debug info consider more locations | ||
|---|---|---|---|
| Product: | gdb | Reporter: | Andre' <andre.poenitz> |
| Component: | symtab | Assignee: | Not yet assigned to anyone <unassigned> |
| Status: | UNCONFIRMED --- | ||
| Severity: | normal | CC: | gdb-prs, jan |
| Priority: | P2 | ||
| Version: | 7.1 | ||
| Target Milestone: | 7.1 | ||
| Host: | i486-linux-gnu | Target: | i486-linux-gnu |
| Build: | i486-linux-gnu | Last reconfirmed: | |
For the "build ID" method of having separate debug info, is ${debug-file-directory}/.build-id/ab/cdef1234.debug is the only location where the debug info is searched for. Even with the possibility to have several locations in debug-file-directory this is difficult to handle as one needs to know in advance (a superset of) the set of shared objects that will be loaded. It would be nice if the build ID method would take the same locations as the debug-link based variant (which does not scale well to large files due to the crc computation).