aboutsummaryrefslogtreecommitdiff
path: root/lldb/source/Plugins/ScriptInterpreter/Python
diff options
context:
space:
mode:
authorPavel Labath <pavel@labath.sk>2024-09-11 10:35:37 +0200
committerAdrian Prantl <aprantl@apple.com>2024-09-19 10:07:13 -0700
commit1f8a3286e065b8cb82628db0d335b3e82b9373fd (patch)
treec1b77aa50c09fbb2ab7dbaca4d962a0f98fd2c0a /lldb/source/Plugins/ScriptInterpreter/Python
parentbeb2ae734830107d28543d172ab43ecc63bb59df (diff)
downloadllvm-1f8a3286e065b8cb82628db0d335b3e82b9373fd.zip
llvm-1f8a3286e065b8cb82628db0d335b3e82b9373fd.tar.gz
llvm-1f8a3286e065b8cb82628db0d335b3e82b9373fd.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')
0 files changed, 0 insertions, 0 deletions