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.
return this->Left::x + 2000;
}
+struct Container
+{
+ PMI member;
+};
+
int
func (int x)
{
null_pmi = NULL;
null_pmf = NULL;
+ Container contain;
+ contain.member = &A::j;
+
pmi = NULL; /* Breakpoint 1 here. */
(diamond.*diamond_pfunc_ptr) (20);
gdb_test "print null_pmf" "$vhn = NULL"
gdb_test "print null_pmf = &A::foo" "$vhn = \\(int \\(A::\\*\\)\\(A \\*( const)?, int\\)\\) $hex <A::foo ?\\(int\\)>"
gdb_test "print null_pmf = 0" "$vhn = NULL"
+
+# Print with a format, bypassing the direct call to the scalar
+# printer. See PR c++/29243.
+gdb_test "print/x contain" " = {member = $hex}"
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. */