public inbox for gdb-prs@sourceware.org
help / color / mirror / Atom feed
From: "cvs-commit at gcc dot gnu.org" <sourceware-bugzilla@sourceware.org>
To: gdb-prs@sourceware.org
Subject: [Bug c++/29896] GDB git doesn't recognize template function name
Date: Tue, 17 Jan 2023 14:15:34 +0000	[thread overview]
Message-ID: <bug-29896-4717-jA4YuiKaGM@http.sourceware.org/bugzilla/> (raw)
In-Reply-To: <bug-29896-4717@http.sourceware.org/bugzilla/>

https://sourceware.org/bugzilla/show_bug.cgi?id=29896

--- Comment #8 from cvs-commit at gcc dot gnu.org <cvs-commit at gcc dot gnu.org> ---
The gdb-13-branch branch has been updated by Tom Tromey
<tromey@sourceware.org>:

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

commit 83d3152401cce0c6fd5cd2d4a140bbf5d89a5d9c
Author: Tom Tromey <tromey@adacore.com>
Date:   Wed Dec 14 14:37:41 2022 -0700

    Fix parameter-less template regression in new DWARF reader

    PR c++/29896 points out a regression in the new DWARF reader.  It does
    not properly handle a case like "break fn", where "fn" is a template
    function.

    This happens because the new index uses strncasecmp to compare.
    However, to make this work correctly, we need a custom function that
    ignores template parameters.

    This patch adds a custom comparison function and fixes the bug.  A new
    test case is included.

    Bug: https://sourceware.org/bugzilla/show_bug.cgi?id=29896

    (cherry picked from commit ac37b79cc440e37fc704d425a6e450afb3c7ee89)

-- 
You are receiving this mail because:
You are on the CC list for the bug.

  parent reply	other threads:[~2023-01-17 14:15 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-12-13  2:05 [Bug c++/29896] New: " vimacs.hacks at gmail dot com
2022-12-13  3:21 ` [Bug c++/29896] " simark at simark dot ca
2022-12-13  3:32 ` vimacs.hacks at gmail dot com
2022-12-13 19:33 ` tromey at sourceware dot org
2022-12-14  0:42 ` tromey at sourceware dot org
2022-12-15 14:28 ` tromey at sourceware dot org
2022-12-15 17:37 ` tromey at sourceware dot org
2022-12-15 19:08 ` tromey at sourceware dot org
2023-01-17 14:06 ` cvs-commit at gcc dot gnu.org
2023-01-17 14:15 ` cvs-commit at gcc dot gnu.org [this message]
2023-01-17 14:15 ` tromey at sourceware dot org
2023-01-18 22:08 ` tromey at sourceware dot org
2023-02-02  3:38 ` brobecker at gnat dot com

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=bug-29896-4717-jA4YuiKaGM@http.sourceware.org/bugzilla/ \
    --to=sourceware-bugzilla@sourceware.org \
    --cc=gdb-prs@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).