From: "François Dumont" <frs.dumont@gmail.com>
To: libstdc++@gcc.gnu.org
Subject: Re: [PATCH] libstdc++: Deliver names of C functions in <stacktrace>
Date: Mon, 12 Dec 2022 22:35:15 +0100 [thread overview]
Message-ID: <7973b22e-791b-a61e-e354-3e6f02e5a731@gmail.com> (raw)
In-Reply-To: <20221212175601.50166-1-gcc@hazardy.de>
On 12/12/22 18:56, Björn Schäpers wrote:
> From: Björn Schäpers <bjoern@hazardy.de>
>
> One could add (), these are not part of __name. One could also try to
> check upfront if __cxa_demangle should be called at all.
>
> -- >8 --
>
> Tested on i686-w64-mingw32.
>
> __cxa_demangle is only to demangle C++ names, for all C functions,
> extern "C" functions, and including main it returns -2, in that case
> just adapt the given name. Otherwise it's kept empty, which doesn't look
> nice in the stacktrace.
>
> libstdc++-v3/ChangeLog:
>
> * include/std/stacktrace (stacktrace_entry::_S_demangle): Use
> raw __name if __cxa_demangle could not demangle it.
>
> Signed-off-by: Björn Schäpers <bjoern@hazardy.de>
> ---
> libstdc++-v3/include/std/stacktrace | 9 ++++++++-
> 1 file changed, 8 insertions(+), 1 deletion(-)
>
> diff --git a/libstdc++-v3/include/std/stacktrace b/libstdc++-v3/include/std/stacktrace
> index 83c6463b0d8..6d4051b9f5b 100644
> --- a/libstdc++-v3/include/std/stacktrace
> +++ b/libstdc++-v3/include/std/stacktrace
> @@ -217,8 +217,15 @@ _GLIBCXX_BEGIN_NAMESPACE_VERSION
> int __status;
> char* __str = __cxxabiv1::__cxa_demangle(__name, nullptr, nullptr,
> &__status);
> - if (__status == 0)
> + switch (__status)
> + {
> + case 0:
> __s = __str;
> + break;
> + case -2:
> + __s = __name;
> + break;
> + }
> __builtin_free(__str);
> return __s;
> }
why not just using __name if __status != 0 ? Everything seems better
than an empty string, no ?
This is what I've done in src/c++11/debug.cc.
next prev parent reply other threads:[~2022-12-12 21:35 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-12-12 17:56 Björn Schäpers
2022-12-12 21:35 ` François Dumont [this message]
2022-12-13 21:02 ` Björn Schäpers
2023-01-14 20:37 ` Jonathan Wakely
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=7973b22e-791b-a61e-e354-3e6f02e5a731@gmail.com \
--to=frs.dumont@gmail.com \
--cc=libstdc++@gcc.gnu.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).