Hi Bogdan, On Sat, Jul 20, 2024 at 09:12:01PM -0400, Bogdan Ciobanu wrote: > Is there any way to serve debugging information stored in .dwo files from a > debuginfod server? For my use case, linking binaries from object files > containing debugging symbols exceeds memory capacity, so object files have > to be stripped ahead of time.
Unfortunately currently no. It shouldn't be that hard though. Each "dwo" has a corresponding dwo_id (or DW_AT_GNU_dwo_id for the DWARF4 GNU DebugFission extension). Which act kind of like a build_id. So we could have a new debuginfod "key" for resolving them. The only wrinkle is that they could come from a .dwo file (or the .o file itself in case of "single" split-dwarf) or a .dwp DWARF package file (which can contain multiple dwos). So some decisions need to be made about what happens if you request a dwo_id that is in a dwp file. You might want to get the full dwp file because it is likely you want more than one. Or you could extract the data and give back a "fake" single .dwo. > Alternatively, is there a way to merge the dwo files in memory into > debugging > information that could be served by the current debuginfod protocol? Also no. Not in memory. There are the dwp files though. Cheers, Mark
