labath wrote: > I suppose could also approach this from the other side and look and see if we > can get this from lldb somehow. Maybe there is enough information that we > could determine from the debugger itself which parts of the file are > expressions and we could make a custom request in lldb-dap for that and call > that from our implementation of EvaluatableExpressionProvider.
LLDB (kind of by design) doesn't parse the source code of a program. In fact, the only reason it touches it at all is to display it to the user. If you delete the source code, every part of the debugger will work just fine, except you won't actually see the code you're debugging. So, no, I don't think there's anything in lldb that would help with that... https://github.com/llvm/llvm-project/pull/146773 _______________________________________________ lldb-commits mailing list lldb-commits@lists.llvm.org https://lists.llvm.org/cgi-bin/mailman/listinfo/lldb-commits
