This is the mail archive of the
gdb-cvs@sourceware.org
mailing list for the GDB project.
gdb and binutils branch master updated. 2d40be181fad7aed4aeabafd36529f3684b8bcab
- From: simark at sourceware dot org
- To: gdb-cvs at sourceware dot org
- Date: 15 Jul 2014 15:20:27 -0000
- Subject: gdb and binutils branch master updated. 2d40be181fad7aed4aeabafd36529f3684b8bcab
This is an automated email from the git hooks/post-receive script. It was
generated because a ref change was pushed to the repository containing
the project "gdb and binutils".
The branch, master has been updated
via 2d40be181fad7aed4aeabafd36529f3684b8bcab (commit)
from ce9e3fe795c05bd7458a1466e14104f489f2b483 (commit)
Those revisions listed above that are new to this repository have
not appeared on any other notification email; so we list those
revisions in full, below.
- Log -----------------------------------------------------------------
https://sourceware.org/git/gitweb.cgi?p=binutils-gdb.git;h=2d40be181fad7aed4aeabafd36529f3684b8bcab
commit 2d40be181fad7aed4aeabafd36529f3684b8bcab
Author: Simon Marchi <simon dot marchi at ericsson dot com>
Date: Thu Jun 19 10:45:33 2014 -0400
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.
-----------------------------------------------------------------------
Summary of changes:
gdb/ChangeLog | 4 ++++
gdb/expprint.c | 19 ++++++++++++++++++-
2 files changed, 22 insertions(+), 1 deletions(-)
hooks/post-receive
--
gdb and binutils