public inbox for libstdc++-cvs@sourceware.org
help / color / mirror / Atom feed
From: Jonathan Wakely <redi@gcc.gnu.org>
To: gcc-cvs@gcc.gnu.org, libstdc++-cvs@gcc.gnu.org
Subject: [gcc r13-5171] libstdc++: Deliver names of C functions in <stacktrace>
Date: Sat, 14 Jan 2023 22:00:22 +0000 (GMT)	[thread overview]
Message-ID: <20230114220022.A68403858425@sourceware.org> (raw)

https://gcc.gnu.org/g:b1c839be8353edfb1951454be3c5a8150f771385

commit r13-5171-gb1c839be8353edfb1951454be3c5a8150f771385
Author: Björn Schäpers <bjoern@hazardy.de>
Date:   Tue Dec 13 22:02:47 2022 +0100

    libstdc++: Deliver names of C functions in <stacktrace>
    
    __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>

Diff:
---
 libstdc++-v3/include/std/stacktrace | 2 ++
 1 file changed, 2 insertions(+)

diff --git a/libstdc++-v3/include/std/stacktrace b/libstdc++-v3/include/std/stacktrace
index 402be3e828e..346c7b14142 100644
--- a/libstdc++-v3/include/std/stacktrace
+++ b/libstdc++-v3/include/std/stacktrace
@@ -219,6 +219,8 @@ _GLIBCXX_BEGIN_NAMESPACE_VERSION
 					       &__status);
       if (__status == 0)
 	__s = __str;
+      else
+	__s = __name;
       __builtin_free(__str);
       return __s;
     }

                 reply	other threads:[~2023-01-14 22:00 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=20230114220022.A68403858425@sourceware.org \
    --to=redi@gcc.gnu.org \
    --cc=gcc-cvs@gcc.gnu.org \
    --cc=libstdc++-cvs@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).