From: Luis Machado <luis.machado@linaro.org>
To: "gdb@sourceware.org" <gdb@sourceware.org>, jan.kratochvil@redhat.com
Subject: Expected output of gdb.cp/no-dmgl-verbose.exp
Date: Mon, 12 Apr 2021 15:16:37 -0300 [thread overview]
Message-ID: <3de907e5-c711-ab80-8b27-f7c13fbde7ec@linaro.org> (raw)
I'm trying to determine why this particular test is failing (for both
aarch64-linux and x86_64-linux on Ubuntu 18.04/20.04) and what the
expected outcome is.
In my case, the only symbol I see for function "f" is the following:
"f(std::__cxx11::basic_string<char, std::char_traits<char>,
std::allocator<char> >)"
There is no "f(std::string)" nor "f(std::basic_string<char,
std::char_traits<char>, std::allocator<char> >)" symbol.
Given we've done quite a few changes to how demangling is applied and
how we match the names, I wonder if this test is no longer meaningful.
Does anyone know?
next reply other threads:[~2021-04-12 18:16 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-04-12 18:16 Luis Machado [this message]
2021-04-12 18:45 ` Keith Seitz
2021-04-12 18:55 ` Luis Machado
2021-04-12 20:07 ` David Blaikie
2021-04-13 8:57 ` Tom de Vries
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=3de907e5-c711-ab80-8b27-f7c13fbde7ec@linaro.org \
--to=luis.machado@linaro.org \
--cc=gdb@sourceware.org \
--cc=jan.kratochvil@redhat.com \
/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).