[Lldb-commits] [libcxx] [lldb] [lldb][libc++] Hide all libc++ implementation details from stacktraces (PR #108870)
Adrian Vogelsgesang via lldb-commits
lldb-commits at lists.llvm.org
Wed Sep 18 16:40:26 PDT 2024
vogelsgesang wrote:
> What I could imagine is to drive this via attributes instead of a heuristic. We could potentially mark implementation details of libc++ as such to control what the debugging experience is like at a much finer grain if we used attributes, but obviously this would also increase complexity in the code and it would be yet another thing that we have to slap on almost every declaration.
Mayve we could also find some other convention. E.g. hiding the `std::*::__detail` namespace. (You could still move all those `__` methods into a different namespace, right? They are not part of the stable ABI, are they?). Using a namespace would have the benefit that
1. you don't need to annotate each individual method, you can simply use a scope
2. we don't need to add a new attribute to clang, dwarf etc.
https://github.com/llvm/llvm-project/pull/108870
More information about the lldb-commits
mailing list