[Lldb-commits] [PATCH] Strip ELF symbol versions from symbol names

[Zachary Turner]

On Thu, Feb 26, 2015 at 10:18 AM Greg Clayton <clayborg at gmail.com> wrote:

>
> > On Feb 26, 2015, at 9:02 AM, Pavel Labath <labath at google.com> wrote:
> >
> > So here is me thinking out loud about this issue...
> >
> > What are the current use cases for the Symbols and SymTabs in lldb?
> >
> > - symbolification (aka looking up a symbol by address): In this case we
> would probably want to output "memcpy@@GLIBC_2.14" because that _is_ the
> name of the symbol in the object file and it also provides the most
> information.
>
> Agreed. I don't like losing information like the real symbol name.
>
> > - symbol resolution (aka looking up a symbol by name): in which
> situations do we need to do this? Currently, I am aware of only one: user
> provided expressions in the "expr" command. Are there any other use cases?
>
> Mostly the expression parser. Users might also try to disassemble a
> function by name and provide "memcpy@@GLIBC_2.14" and it would be nice if
> this worked (which wouldn't happen if we stripped this down to just
> "memcpy".
>
Someday I plan to add a symbol search command that will be able to find
symbols by regex if nobody beats me to it.  That would also be a consumer
of symbol names.
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.llvm.org/pipermail/lldb-commits/attachments/20150226/7ee87246/attachment.html>