Use gdb's 'print' command to access dumper output.
Simple solution after all. This idea got initially dropped early in the process because it does not handle binary data and using x/x was way to slow. But since we use only printable characters now thanks to base64 encoding etc using 'p' becomes feasible again and simplifies the process vastly as no additional communication channel is needed anymore.
Showing
- bin/gdbmacros/gdbmacros.cpp 26 additions, 24 deletionsbin/gdbmacros/gdbmacros.cpp
- src/plugins/debugger/debuggerplugin.cpp 1 addition, 1 deletionsrc/plugins/debugger/debuggerplugin.cpp
- src/plugins/debugger/gdbengine.cpp 190 additions, 3 deletionssrc/plugins/debugger/gdbengine.cpp
- src/plugins/debugger/gdbengine.h 3 additions, 0 deletionssrc/plugins/debugger/gdbengine.h
- src/plugins/debugger/gdbmi.cpp 15 additions, 15 deletionssrc/plugins/debugger/gdbmi.cpp
- src/plugins/debugger/gdbmi.h 8 additions, 14 deletionssrc/plugins/debugger/gdbmi.h
Loading
Please register or sign in to comment