public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "cvs-commit at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug libstdc++/14493] std::bad_alloc::what() does not explain what happened
Date: Thu, 27 Apr 2023 23:04:45 +0000 [thread overview]
Message-ID: <bug-14493-4-ZSXjlwvdvP@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-14493-4@http.gcc.gnu.org/bugzilla/>
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=14493
--- Comment #33 from CVS Commits <cvs-commit at gcc dot gnu.org> ---
The releases/gcc-10 branch has been updated by Jonathan Wakely
<redi@gcc.gnu.org>:
https://gcc.gnu.org/g:c73f20e67ee8d268bf0dfd6732c1bd3e79e098ca
commit r10-11323-gc73f20e67ee8d268bf0dfd6732c1bd3e79e098ca
Author: Jonathan Wakely <jwakely@redhat.com>
Date: Tue Apr 4 12:04:14 2023 +0100
libstdc++: Fix outdated docs about demangling exception messages
The string returned by std::bad_exception::what() hasn't been a mangled
name since PR libstdc++/14493 was fixed for GCC 4.2.0, so remove the
docs showing how to demangle it.
libstdc++-v3/ChangeLog:
* doc/xml/manual/extensions.xml: Remove std::bad_exception from
example program.
* doc/html/manual/ext_demangling.html: Regenerate.
(cherry picked from commit 688d126b69215db29774c249b052e52d765782b3)
next prev parent reply other threads:[~2023-04-27 23:04 UTC|newest]
Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <bug-14493-4@http.gcc.gnu.org/bugzilla/>
2023-04-04 11:17 ` cvs-commit at gcc dot gnu.org
2023-04-20 13:57 ` cvs-commit at gcc dot gnu.org
2023-04-27 22:01 ` cvs-commit at gcc dot gnu.org
2023-04-27 23:04 ` cvs-commit at gcc dot gnu.org [this message]
[not found] <bug-14493-5724@http.gcc.gnu.org/bugzilla/>
2007-01-30 0:34 ` pcarlini at suse dot de
2007-01-30 0:54 ` pinskia at gcc dot gnu dot org
2007-01-30 0:58 ` pcarlini at suse dot de
2007-01-30 1:30 ` gdr at cs dot tamu dot edu
2007-01-30 1:42 ` pcarlini at suse dot de
2007-01-30 2:11 ` gdr at cs dot tamu dot edu
2007-01-30 2:21 ` pcarlini at suse dot de
2007-01-30 3:53 ` gdr at cs dot tamu dot edu
2007-02-01 2:18 ` lopresti at gmail dot com
2007-02-01 13:37 ` paolo at gcc dot gnu dot org
2007-02-01 13:39 ` pcarlini at suse dot de
2007-02-01 15:57 ` paolo at gcc dot gnu dot org
2007-02-01 15:58 ` pcarlini at suse dot de
2004-03-08 22:10 [Bug libstdc++/14493] New: new: No std::bad_alloc::what() const debian-gcc at lists dot debian dot org
2004-04-27 13:54 ` [Bug libstdc++/14493] std::bad_alloc::what() does not explain what happened pinskia at gcc dot gnu dot org
2004-08-05 14:37 ` pcarlini at suse dot de
2004-08-05 15:01 ` pcarlini at suse dot de
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-14493-4-ZSXjlwvdvP@http.gcc.gnu.org/bugzilla/ \
--to=gcc-bugzilla@gcc.gnu.org \
--cc=gcc-bugs@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).