diff options
author | 2010-07-21 19:27:05 -0500 | |
---|---|---|
committer | 2010-07-21 19:27:05 -0500 | |
commit | fb82c0ff27b2c40c6f7a3d1a94cafb154591fa80 (patch) | |
tree | 98e49fdc15e9db7eb45e91571ca6187f9a5cf516 /tools/perf/util/scripting-engines/trace-event-python.c | |
parent | kdb: break out of kdb_ll() when command is terminated (diff) | |
download | linux-dev-fb82c0ff27b2c40c6f7a3d1a94cafb154591fa80.tar.xz linux-dev-fb82c0ff27b2c40c6f7a3d1a94cafb154591fa80.zip |
repair gdbstub to match the gdbserial protocol specification
The gdbserial protocol handler should return an empty packet instead
of an error string when ever it responds to a command it does not
implement.
The problem cases come from a debugger client sending
qTBuffer, qTStatus, qSearch, qSupported.
The incorrect response from the gdbstub leads the debugger clients to
not function correctly. Recent versions of gdb will not detach correctly as a result of this behavior.
Signed-off-by: Jason Wessel <jason.wessel@windriver.com>
Signed-off-by: Dongdong Deng <dongdong.deng@windriver.com>
Diffstat (limited to 'tools/perf/util/scripting-engines/trace-event-python.c')
0 files changed, 0 insertions, 0 deletions