aboutsummaryrefslogtreecommitdiff
path: root/gdb/target.c
diff options
context:
space:
mode:
authorSimon Marchi <simon dot marchi at ericsson dot com>2014-06-19 10:45:33 -0400
committerSimon Marchi <simon.marchi@ericsson.com>2014-07-15 11:18:04 -0400
commit2d40be181fad7aed4aeabafd36529f3684b8bcab (patch)
treeb7294c39f91cb1889ff4b915b3812c42d23a0e25 /gdb/target.c
parentce9e3fe795c05bd7458a1466e14104f489f2b483 (diff)
downloadgdb-2d40be181fad7aed4aeabafd36529f3684b8bcab.zip
gdb-2d40be181fad7aed4aeabafd36529f3684b8bcab.tar.gz
gdb-2d40be181fad7aed4aeabafd36529f3684b8bcab.tar.bz2
Handle OP_STRING in dump_subexp_body_standard
For some reason, OP_STRING is not handled in dump_subexp_body_standard. This makes the output of "set debug expression 1" very bad when a string is involved. Example: (gdb) set debug expression 1 (gdb) print "hello" ... (random garbage, possibly segfault) This commit handles OP_STRING and skips the appropriate number of exp elements. The line corresponding to the string now looks like: 0 OP_STRING Language-specific string type: 0 gdb/ChangeLog: 2014-07-15 Simon Marchi <simon.marchi@ericsson.com> * expprint.c (dump_subexp_body_standard): Handle OP_STRING.
Diffstat (limited to 'gdb/target.c')
0 files changed, 0 insertions, 0 deletions