public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "pcarlini at suse dot de" <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: Tue, 30 Jan 2007 00:34:00 -0000 [thread overview]
Message-ID: <20070130003425.12451.qmail@sourceware.org> (raw)
In-Reply-To: <bug-14493-5724@http.gcc.gnu.org/bugzilla/>
------- Comment #18 from pcarlini at suse dot de 2007-01-30 00:34 -------
Implementing the really trivial solution of providing what() members returning
"std::bad_alloc", "std::bad_cast", "std::bad_typeid", and "std::bad_exception".
--
pcarlini at suse dot de changed:
What |Removed |Added
----------------------------------------------------------------------------
AssignedTo|unassigned at gcc dot gnu |pcarlini at suse dot de
|dot org |
Status|NEW |ASSIGNED
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=14493
next parent reply other threads:[~2007-01-30 0:34 UTC|newest]
Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <bug-14493-5724@http.gcc.gnu.org/bugzilla/>
2007-01-30 0:34 ` pcarlini at suse dot de [this message]
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
[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
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=20070130003425.12451.qmail@sourceware.org \
--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).