llvm-project/lldb/unittests/Process
Pavel Labath e2f1fe361a [lldb/Utility] Introduce UnimplementedError
This is essentially a replacement for the PacketUnimplementedError
previously present in the gdb-remote server code.

The reason I am introducing a generic error is because I wanted the
native process classes to be able to signal that they do not support
some functionality. They could not use PacketUnimplementedError as they
are independent of a specific transport protocol. Putting the error
class in the the native process code was also not ideal because the
gdb-remote code is also used for lldb-server's platform mode, which does
not (should not) know how to debug individual processes.

I'm putting it under Utility, as I think it can be generally useful for
notifying about unsupported/unimplemented functionality (and in
particular, for programatically testing whether something is
unsupported).

Differential Revision: https://reviews.llvm.org/D89121
2020-10-12 13:46:17 +02:00
..
Linux [lldb] Get rid of helper CMake variables for Python 2020-08-17 08:47:52 -07:00
POSIX [lldb] Use modern CMake to avoid repetition (NFC) 2020-08-10 22:29:40 -07:00
gdb-remote [lldb/Utility] Introduce UnimplementedError 2020-10-12 13:46:17 +02:00
minidump Load correct module for linux and android when duplicates exist in minidump. 2020-08-26 15:48:34 -07:00
CMakeLists.txt [lldb/Test] Fix unittest name 2020-06-12 14:01:14 -07:00
ProcessEventDataTest.cpp [lldb] Check if thread was suspended during previous stop added. 2020-06-11 15:02:46 -07:00