diff options
| author | Pavel Labath <pavel@labath.sk> | 2024-09-11 10:35:37 +0200 |
|---|---|---|
| committer | Adrian Prantl <aprantl@apple.com> | 2024-09-18 14:53:42 -0700 |
| commit | a7c174502aef45b2d33291129cce10c085fef944 (patch) | |
| tree | 7cd3392df213122287aacd358406c33c44910068 /lldb/source/Plugins/ScriptInterpreter/Python/PythonDataObjects.cpp | |
| parent | e0ad34e56590fa2e6ffdf617e044de7eadee2139 (diff) | |
| download | llvm-a7c174502aef45b2d33291129cce10c085fef944.zip llvm-a7c174502aef45b2d33291129cce10c085fef944.tar.gz llvm-a7c174502aef45b2d33291129cce10c085fef944.tar.bz2 | |
[lldb] Only send "posix" error codes through the gdb-remote protocol
The other side has no way of telling which namespace do these codes
belong to, so mashing them all together is not very helpful.
I'm mainly doing this to simplify some code in a pending patch
<https://github.com/llvm/llvm-project/pull/106774/files#r1752628604>,
and I've picked the posix error category semi-randomly. If we wanted to
be serious about assigning meaning to these error codes, we should
create a special error category for "gdb errors".
Diffstat (limited to 'lldb/source/Plugins/ScriptInterpreter/Python/PythonDataObjects.cpp')
0 files changed, 0 insertions, 0 deletions