public inbox for gdb-cvs@sourceware.org
help / color / mirror / Atom feed
From: Bruno Larsen <blarsen@sourceware.org>
To: gdb-cvs@sourceware.org
Subject: [binutils-gdb] gdb: Fix regressions caused by 041de3d73aa121f2ff0c077213598963bfb34b79
Date: Thu, 10 Nov 2022 17:09:26 +0000 (GMT)	[thread overview]
Message-ID: <20221110170927.352FC3858D3C@sourceware.org> (raw)

https://sourceware.org/git/gitweb.cgi?p=binutils-gdb.git;h=05e8d17b8b49065a104277f4df6bfe5e72e83862

commit 05e8d17b8b49065a104277f4df6bfe5e72e83862
Author: Bruno Larsen <blarsen@redhat.com>
Date:   Thu Nov 10 17:58:58 2022 +0100

    gdb: Fix regressions caused by 041de3d73aa121f2ff0c077213598963bfb34b79
    
    Commit 041de3d73aa changed the output format of all error messages when
    GDB couldn't determine a compatible overload for a given function, but
    it was only supposed to change if the failure happened due to incomplete
    types. This commit removes the stray . that was added

Diff:
---
 gdb/valops.c | 4 ++--
 1 file changed, 2 insertions(+), 2 deletions(-)

diff --git a/gdb/valops.c b/gdb/valops.c
index 2b789cd76f4..e90c3947b8d 100644
--- a/gdb/valops.c
+++ b/gdb/valops.c
@@ -2979,12 +2979,12 @@ find_overload_match (gdb::array_view<value *> args,
     {
       std::string hint = incomplete_type_hint (args);
       if (method == METHOD)
-	error (_("Cannot resolve method %s%s%s to any overloaded instance.%s"),
+	error (_("Cannot resolve method %s%s%s to any overloaded instance%s"),
 	       obj_type_name,
 	       (obj_type_name && *obj_type_name) ? "::" : "",
 	       name, hint.c_str ());
       else
-	error (_("Cannot resolve function %s to any overloaded instance.%s"),
+	error (_("Cannot resolve function %s to any overloaded instance%s"),
 	       func_name, hint.c_str ());
     }
   else if (match_quality == NON_STANDARD)

                 reply	other threads:[~2022-11-10 17:09 UTC|newest]

Thread overview: [no followups] expand[flat|nested]  mbox.gz  Atom feed

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=20221110170927.352FC3858D3C@sourceware.org \
    --to=blarsen@sourceware.org \
    --cc=gdb-cvs@sourceware.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).