differentiate reconstructed symbol table based entries
m4b opened this issue · 6 comments
I realized that when the debuginfo is missing for a symbol table entry, ddbug still outputs the entry with whatever it finds in the symbol table.
This is great! However, it did mislead me by thinking the debuginfo was emitted (when it wasn't), and this was something I was specifically investigating.
Is it possible to add for these cases something like a (no debug info) field or (reconstructed) or something, in order to flag it?
It should be putting these in a <symtab> unit.
Ah, I didn't even check for that/would have suspected it.
We can close then I guess, makes sense. To be clear anything not found in dwarf stuff is put into synthetic unit, whose values/members are extracted directly from the binaries symbol table, yes?
Would be nice to have a blurb about this somewhere, but not sure where that would go.
EDIT
also my usecase was i was grepping symbols with a -C 5 so i'd still have to check they're after symtab unit. It's not really important though, just thought I'd add that.
To be clear anything not found in dwarf stuff is put into synthetic unit, whose values/members are extracted directly from the binaries symbol table, yes?
Yes.
I do need to write some sort of documentation/manual that explains things like this.
I understand your use case, but it's possibly a bit specialized. I think the issue is you're coming from an angle of wanting to debug the DWARF generation, instead of just wanting to extract information (which is mostly what I use it for). I could add an option to disable usage of the symbol table, but I probably don't want to do anything more intrusive than that.
One thing you could do is if you know which unit the entry is in, then you could pass an option to ddbug to only display that unit.
yea, unit maybe could work, but honestly your time is probably spent elsewhere and other features. now that i know about symtab unit, i just know what to look out for