summaryrefslogtreecommitdiff
path: root/gdb/testsuite/gdb.mi/mi-cmd-user-context.exp
diff options
context:
space:
mode:
authorLuis Machado <luis.machado@arm.com>2022-03-31 16:45:53 +0100
committerLuis Machado <luis.machado@arm.com>2022-04-05 08:44:19 +0100
commitd5ce6f2dcacf9809fb7a29a69c4b98e0320c3c94 (patch)
treedf1744e789b12e5b1fc4a55e55c9b48269fd0f72 /gdb/testsuite/gdb.mi/mi-cmd-user-context.exp
parent27f9f649753b8c4bd4c40bde0f49d916c222a16a (diff)
downloadbinutils-gdb-d5ce6f2dcacf9809fb7a29a69c4b98e0320c3c94.tar.gz
Fix qRcmd error code parsing
Someone at IRC spotted a bug in qRcmd handling. This looks like an oversight or it is that way for historical reasons. The code in gdb/remote.c:remote_target::rcmd uses isdigit instead of isxdigit. One could argue that we are expecting decimal numbers, but further below we use fromhex (). Update the function to use isxdigit instead and also update the documentation. I see there are lots of other cases of undocumented number format for error messages, mostly described as NN instead of nn. For now I'll just update this particular function.
Diffstat (limited to 'gdb/testsuite/gdb.mi/mi-cmd-user-context.exp')
0 files changed, 0 insertions, 0 deletions