Michael137 wrote: When you're stopped in a frame and you have libc++ frames above you in the backtrace, you're either stopped in a callback (like `std::function`, `std::make_unique`, `std::sort`), or you're deliberately stepping into libc++ code. For the latter, you probably don't want to hide any of the implementation details (though the libc++ devs might be able to comment better on their workflow here). I would find it weird if I stepped into a series of function calls manually but the backtrace omitted my path down.
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? Not sure. Wdyt? https://github.com/llvm/llvm-project/pull/108870 _______________________________________________ lldb-commits mailing list lldb-commits@lists.llvm.org https://lists.llvm.org/cgi-bin/mailman/listinfo/lldb-commits
