Support for mangled names about dwarf_import HOT 3 CLOSED

Hey Oskar!

Do you have an example? I'm not able to reproduce what you're describing; function symbols with updated names maintain their raw_name fields in my test binaries.

from dwarf_import.

I have spent some time delving into the fb build system to see what exactly is happening, but I still don't know exactly why this is happening or if it's even something you can address:

1. I get the unstripped library and disassemble it in binja
2. The function at 0xba0 has a name _5
3. I run the dwarf plugin and now the unmangled name is operator()(class* this)
4. The underlying "mangled name" is still _5 but running nm or readelf will show the 'true' mangled name as _ZZN8facebook5build13getAndroidSdkEvENK3$_0clEv

If this is not relevant to this plugin feel free to close and dismiss this task. I was thinking this plugin would overwrite the mangled name, but now that I am typing it, that doesn't make sense.

from dwarf_import.

That is very strange. If you have a sample you're able to share, I'd be happy to look in to it more.

Are you looking at all the forms of the symbol's name? function.symbol.short_name is usually what get displayed, where as function.symbol.raw_name should be the actual original mangled name. If that's not the case, I suspect it would be a bug in our ELF loader (recently open sourced).

from dwarf_import.