[Lldb-commits] [libcxx] [lldb] [lldb][libc++] Hide all libc++ implementation details from stacktraces (PR #108870)

[Adrian Vogelsgesang via lldb-commits]

vogelsgesang wrote:

> We really should add a "disable" to the frame recognizers

Merged #109219

> I wonder if a heuristic for the callback case could be: mark all but the first libc++ entry point as an implementation detail. Would this be even more aggressive? Also, the implementation of this might be a bit awkward. Not sure. Wdyt?

I combined your approach with the `__`-based heuristic. I am quite happy with the result. It's more robust now, as can be seen by the updated test expectations for `ranges::sort`: The top-level `std::__1::ranges::__sort::operator()` is no longer hidden

https://github.com/llvm/llvm-project/pull/108870