Reminder : the next LLVM social in Paris will happen next week, on January
30th, 2018.
Everyone interested in LLVM, Clang, lldb, Polly, lld, ... is invited to
join.
Event details, including registration (free but mandatory) at
http://www.meetup.com/LLVM-Clang-social
This meetup agenda :
- Dimit
I have an issue where I am debugging a C++ binary that is around 250MB in size.
It contains some mangled names that are crazy:
_ZNK3shk6detail17CallbackPublisherIZNS_5ThrowERKNSt15__exception_ptr13exception_ptrEEUlOT_E_E9SubscribeINS0_9ConcatMapINS0_18CallbackSubscriberIZNS_6GetAllIiNS1_IZZNS_9Co
What about doing a partial demangle? Take at most 1024 (for example)
characters from the mangled name, demangle that, and then display ... at
the end.
On Wed, Jan 24, 2018 at 3:48 PM Greg Clayton via lldb-dev <
lldb-dev@lists.llvm.org> wrote:
> I have an issue where I am debugging a C++ binary
If you just cut off the string, then it might not demangle without an error if
you truncate the mangled string at a specific point...
> On Jan 24, 2018, at 3:52 PM, Zachary Turner wrote:
>
> What about doing a partial demangle? Take at most 1024 (for example)
> characters from the mangled na
That's true, but shouldn't it be possible to demangle up until the last
point you got something meaningful? (I don't know the details of itanium
mangling, just assuming this is possible)
On Wed, Jan 24, 2018 at 3:54 PM Greg Clayton wrote:
> If you just cut off the string, then it might not dema
> On Jan 24, 2018, at 4:14 PM, Zachary Turner wrote:
>
> That's true, but shouldn't it be possible to demangle up until the last point
> you got something meaningful? (I don't know the details of itanium mangling,
> just assuming this is possible)
anywhere you cut the string many things can
