From f8bfbf22251f6c2772a9a1059c3180c638ad2830 Mon Sep 17 00:00:00 2001 From: Tom Tromey Date: Tue, 3 Oct 2017 08:26:16 -0600 Subject: [PATCH] Fix incorrect string_printf use in utils.c I made a mistake earlier and used string_printf where I should have used string_vprintf. I'm checking this in as obvious. 2017-10-03 Tom Tromey * utils.c (internal_vproblem): Use string_vprintf. --- gdb/ChangeLog | 4 ++++ gdb/utils.c | 2 +- 2 files changed, 5 insertions(+), 1 deletion(-) diff --git a/gdb/ChangeLog b/gdb/ChangeLog index 439df4a5f5d..6e135f2a03c 100644 --- a/gdb/ChangeLog +++ b/gdb/ChangeLog @@ -1,3 +1,7 @@ +2017-10-03 Tom Tromey + + * utils.c (internal_vproblem): Use string_vprintf. + 2017-10-03 Tom Tromey * printcmd.c (info_symbol_command): Use std::string. diff --git a/gdb/utils.c b/gdb/utils.c index 03b66c4f9e6..118fcc3e6d0 100644 --- a/gdb/utils.c +++ b/gdb/utils.c @@ -425,7 +425,7 @@ internal_vproblem (struct internal_problem *problem, style similar to a compiler error message. Include extra detail so that the user knows that they are living on the edge. */ { - std::string msg = string_printf (fmt, ap); + std::string msg = string_vprintf (fmt, ap); reason = string_printf ("%s:%d: %s: %s\n" "A problem internal to GDB has been detected,\n" "further debugging may prove unreliable.", -- 2.30.2