https://sourceware.org/bugzilla/show_bug.cgi?id=20876
Nick Clifton <nickc at redhat dot com> changed: What |Removed |Added ---------------------------------------------------------------------------- Attachment #9746|0 |1 is obsolete| | --- Comment #4 from Nick Clifton <nickc at redhat dot com> --- Created attachment 9748 --> https://sourceware.org/bugzilla/attachment.cgi?id=9748&action=edit Proposed patch Hi Matthias, OK, here is a revised patch. Please let me know what you think. I have not added build-id verification as I am lazy, but that can be done if you are happy with the rest of the patch. More controversially however, I have not restricted the path generation to absolute paths. The reason is basically testing. If the build-id based debug info files *have* to be installed into admin controlled parts of the file system then it is not going to be possible to test the feature as an ordinary user. (See the addition to objdump.exp in the updated patch for an example of how I envisage testing the feature currently). Is it such a bad thing to be able to load locally stored build-id based debug info files ? It makes testing possible, and I imagine that it would be quite useful in development too. If the user wants to debug a built, but not installed, application (which uses build-id based separate debug files), then all that they need to do is to make sure that the files are in the correct .build-id/NN directories and away they go. Cheers Nick -- You are receiving this mail because: You are on the CC list for the bug. _______________________________________________ bug-binutils mailing list bug-binutils@gnu.org https://lists.gnu.org/mailman/listinfo/bug-binutils