public inbox for gdb-prs@sourceware.org
help / color / mirror / Atom feed
From: "trass3r at gmail dot com" <sourceware-bugzilla@sourceware.org>
To: gdb-prs@sourceware.org
Subject: [Bug c++/26122] gdb fails to demangle a name
Date: Wed, 02 Sep 2020 16:18:37 +0000	[thread overview]
Message-ID: <bug-26122-4717-bcBpjAqTCh@http.sourceware.org/bugzilla/> (raw)
In-Reply-To: <bug-26122-4717@http.sourceware.org/bugzilla/>

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

trass3r <trass3r at gmail dot com> changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
                 CC|                            |trass3r at gmail dot com

--- Comment #1 from trass3r <trass3r at gmail dot com> ---
Confirmed on trunk but it has nothing to do with not being able to demangle.
It happens with a simple std::make_unique<int>(5) call and regex ^std:: too.

The problem is that in infrun.c
function_name_is_marked_for_skip (ecs->stop_func_name,
actually gets the mangled name unlike in other calls to that function.

https://sourceware.org/git/?p=binutils-gdb.git;a=blob;f=gdb/infrun.c;h=938bc081a1c96ab0551046b6cccc777bd40dd78e;hb=HEAD#l6859

The only workaround is to match the mangled name, 'skip -rfu ^_ZSt' in my case.

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

      reply	other threads:[~2020-09-02 16:18 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-06-16 15:18 [Bug c++/26122] New: " mgaudet at mozilla dot com
2020-09-02 16:18 ` trass3r at gmail dot com [this message]

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-26122-4717-bcBpjAqTCh@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).