Repository navigation
DWARF Import #3206
Description
We started to create a rust plugin that could use the DebugInfo APIs to parse dwarf information (indeed, it's what DebugInfo was designed for) but it was not completed. The current plugin has a number of limitations that would be eliminated by finishing this plugin.
Activity
[-]finish dwarf plugin migration to rust[/-][+]DWARF Import[/+]DWARF Import DebugInfo Plugin
6 remaining items
ElykDeer commentedon Jul 10, 2023
This is implemented as off 3.5.4377-dev, but disabled by default. To enable the new plugin, enable the setting
corePlugins.dwarfImport:After that, any ELF files that contain DWARF info should automatically apply at load time. If you'd like to apply debug info from a different file (
.dwo,.debugfiles), you can use the load settinganalysis.debugInfo.externalor use "Analysis" -> "Import Debug Info from External File".DWARF Import DebugInfo Plugin
fuzyll commentedon Aug 22, 2023
Reopening this as I'm continuing to have crashes on a lot of things I'm putting through it and we were hoping to be able to have this turned on by default for the upcoming 3.5 release.
We can close this again once we've got unit tests committed and have run this across a reasonable corpus of inputs. I believe we'll also need some documentation for how to use this with #3643.
ElykDeer commentedon Sep 27, 2023
Documentation exists here. I've now run this on all the debug files in the Debian corpus (~1TB of files), with no crashes. Parsed ~0.5B Types/Functions/Data Vars.
psifertex commentedon Sep 27, 2023
I think the only remaining task should be the unit test and it's good to enable by default on dev and close.
ElykDeer commentedon Sep 29, 2023
We talked about this over Slack, but just putting it here as well that there are unit tests.
ElykDeer commentedon Oct 25, 2023
The last thing holding this issue open is a round-trip unit test with our DWARF Export plugin, which is blocked by the issue just above, #4700.
ElykDeer commentedon Oct 30, 2023
I worked around #4700 by shelling out to a subprocess. Would still be nice to fix that, but the round trip unit test is now in and I believe we can consider this issue closed.