aboutsummaryrefslogtreecommitdiff
path: root/gdb/valprint.c
diff options
context:
space:
mode:
authorTom Tromey <tromey@adacore.com>2022-10-18 11:32:52 -0600
committerTom Tromey <tromey@adacore.com>2022-10-31 08:49:06 -0600
commit86430497337968e6163aef370c6312e7b5ed6504 (patch)
treecc8e805321dc54a833dcc8fea91acf661a444373 /gdb/valprint.c
parent1bf074fb6b5474f94e315d7047c0500535f0a2ef (diff)
downloadgdb-86430497337968e6163aef370c6312e7b5ed6504.zip
gdb-86430497337968e6163aef370c6312e7b5ed6504.tar.gz
gdb-86430497337968e6163aef370c6312e7b5ed6504.tar.bz2
Fix regression in pointer-to-member printing
PR c++/29243 points out that "info func" on a certain C++ executable will cause an infinite loop in gdb. I tracked this down to a bug introduced by commit 6b5a7bc76 ("Handle member pointers directly in generic_value_print"). Before this commit, the C++ code to print a member pointer would wind up calling value_print_scalar_formatted; but afterward it simply calls generic_value_print and gets into a loop. This patch restores the previous behavior and adds a regression test.
Diffstat (limited to 'gdb/valprint.c')
-rw-r--r--gdb/valprint.c2
1 files changed, 1 insertions, 1 deletions
diff --git a/gdb/valprint.c b/gdb/valprint.c
index 25db57e..48d611e 100644
--- a/gdb/valprint.c
+++ b/gdb/valprint.c
@@ -879,7 +879,7 @@ generic_value_print_memberptr
cp_print_class_member (valaddr, type, stream, "&");
}
else
- generic_value_print (val, stream, recurse, options, decorations);
+ value_print_scalar_formatted (val, options, 0, stream);
}
/* See valprint.h. */