aboutsummaryrefslogtreecommitdiff
path: root/gdb/printcmd.c
diff options
context:
space:
mode:
authorSergio Durigan Junior <sergiodj@redhat.com>2020-03-01 18:15:53 -0500
committerSergio Durigan Junior <sergiodj@redhat.com>2020-03-03 11:28:09 -0500
commit7b973adce2b486518d3150db257b179e1b9a5d33 (patch)
treede4cfc353682bb8fbb59c2ae77f4025386ecf3df /gdb/printcmd.c
parent5be2b2f549b0ba0743938d1d74708d79cf42dc0f (diff)
downloadgdb-7b973adce2b486518d3150db257b179e1b9a5d33.zip
gdb-7b973adce2b486518d3150db257b179e1b9a5d33.tar.gz
gdb-7b973adce2b486518d3150db257b179e1b9a5d33.tar.bz2
Fix printf of a convenience variable holding an inferior address
Back at: commit 1f6f6e21fa86dc3411a6498608f32e9eb24b7851 Author: Philippe Waroquiers <philippe.waroquiers@skynet.be> Date: Mon Jun 10 21:41:51 2019 +0200 Ensure GDB printf command can print convenience var strings without a target. GDB was extended in order to allow the printing of convenience variables that are strings without a target. However, this introduced a regression that hasn't been caught by our testsuite (because there were no tests for it). The problem happens when we try to print a convenience variable that holds the address of a string in the inferior. The following two-liners can reproduce the issue: $ echo -e 'int main(){const char a[]="test";return 0;}' | gcc -x c - -O0-g3 $ ./gdb/gdb --data-directory ./gdb/data-directory -q ./a.out -ex 'start' -ex 'set $x = (const char *) (&a[0] + 2)' -ex 'printf "%s\n", $x' After some investigation, I found that the problem happens on printcmd.c:printf_c_string. In the case above, we're taking the first branch of the 'if' condition, which assumes that there will be a value to be printed at "value_contents (value)". There isn't. We actually need to obtain the address that the variable points to, and read the contents from memory. It seems to me that we should avoid this branch if the TYPE_CODE of "value_type (value)" is TYPE_CODE_PTR (i.e., a pointer to the inferior's memory). This is what this patch does. I took the liberty to extend the current testcase under gdb.base/printcmds.exp and create a test that exercises this scenario. No regressions have been found on Buildbot. gdb/ChangeLog: 2020-03-03 Sergio Durigan Junior <sergiodj@redhat.com> * printcmd.c (print_c_string): Check also for TYPE_CODE_PTR when verifying if dealing with a convenience variable. gdb/testsuite/ChangeLog: 2020-03-03 Sergio Durigan Junior <sergiodj@redhat.com> * gdb.base/printcmds.exp: Add test to verify printf of a variable holding an address.
Diffstat (limited to 'gdb/printcmd.c')
-rw-r--r--gdb/printcmd.c3
1 files changed, 2 insertions, 1 deletions
diff --git a/gdb/printcmd.c b/gdb/printcmd.c
index 7970414..78d8d3d 100644
--- a/gdb/printcmd.c
+++ b/gdb/printcmd.c
@@ -2260,7 +2260,8 @@ printf_c_string (struct ui_file *stream, const char *format,
{
const gdb_byte *str;
- if (VALUE_LVAL (value) == lval_internalvar
+ if (TYPE_CODE (value_type (value)) != TYPE_CODE_PTR
+ && VALUE_LVAL (value) == lval_internalvar
&& c_is_string_type_p (value_type (value)))
{
size_t len = TYPE_LENGTH (value_type (value));