================
@@ -36,9 +36,7 @@ DAP::DAP()
{{"cpp_catch", "C++ Catch", lldb::eLanguageTypeC_plus_plus},
{"cpp_throw", "C++ Throw", lldb::eLanguageTypeC_plus_plus},
{"objc_catch", "Objective-C Catch", lldb::eLanguageTypeObjC},
- {"objc_throw", "Objective-C Throw", lldb::eLanguageTypeObjC},
- {"swift_catch", "Swift Catch", lldb::eLanguageTypeSwift},
- {"swift_throw", "Swift Throw", lldb::eLanguageTypeSwift}}),
+ {"objc_throw", "Objective-C Throw", lldb::eLanguageTypeObjC}}),
----------------
oontvoo wrote:
Thanks for the detailed suggestions! Makes sense!
For ObjC, just to clarify, the intention of hiding the filters was NOT because
the debugger didn't support it - the intention was to avoid
clustering/confusing users - that is, if they're not debugging ObjC, there's no
reason to show the objc filters. (And we infer this by checking if they're
debugging on a mac - it's theoretically possible they're cross debugging objc
from a non-mac but in practice I don't think it's likely )
Does this seem reasonable?
https://github.com/llvm/llvm-project/pull/87550
_______________________________________________
lldb-commits mailing list
lldb-commits@lists.llvm.org
https://lists.llvm.org/cgi-bin/mailman/listinfo/lldb-commits
