public inbox for gcc-bugs@sourceware.org help / color / mirror / Atom feed
From: "phil at jaj dot com" <gcc-bugzilla@gcc.gnu.org> To: gcc-bugs@gcc.gnu.org Subject: [Bug libstdc++/14493] No std::bad_alloc::what() const Date: Tue, 09 Mar 2004 19:32:00 -0000 [thread overview] Message-ID: <20040309193214.14091.qmail@sources.redhat.com> (raw) In-Reply-To: <20040308221042.14493.debian-gcc@lists.debian.org> ------- Additional Comments From phil at jaj dot com 2004-03-09 19:32 ------- Subject: Re: Bug#236912: No std::bad_alloc::what() const On Tue, Mar 09, 2004 at 07:32:32PM +0100, Jeroen T. Vermeulen wrote: > On Tue, Mar 09, 2004 at 06:14:59AM +0100, Matthias Klose wrote: > > > > More to the point, it doesn't matter how it's implemented, and the user > > > should not care. It only matters that > > > > > > std::bad_alloc foo; > > > std::cerr << foo.what() << std::endl; > > > > > > works, which the submitter didn't apparently try. Looking at the original > > Apparently whoever said this hasn't seen the bug report, and it got > rephrased somewhere along the line. No, I read it. > I was wrong in my assumption that > std::bad_alloc should override what(), but the problem remains: the > message coming out of what(), "St9bad_alloc" is incomprehensible to > a normal user. If you mean to complain about X, then don't complain about Y. Don't title your bug reports "Y is missing" when you find you don't like the behavior of X. Don't assume that X and Y have anything to do with one another. The output of what() is described in the library documentation. There is also documentation provided on how to run the demangler on the string, e.g., std::cerr << the_demangler_function(foo.what()) << std::endl; -- http://gcc.gnu.org/bugzilla/show_bug.cgi?id=14493
next prev parent reply other threads:[~2004-03-09 19:32 UTC|newest] Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top 2004-03-08 22:10 [Bug libstdc++/14493] New: new: " debian-gcc at lists dot debian dot org 2004-03-08 22:37 ` [Bug libstdc++/14493] " pinskia at gcc dot gnu dot org 2004-03-08 23:15 ` [Bug libstdc++/14493] " bangerth at dealii dot org 2004-03-09 4:14 ` pme at gcc dot gnu dot org 2004-03-09 4:14 ` phil at jaj dot com 2004-03-09 4:45 ` zack at gcc dot gnu dot org 2004-03-09 5:19 ` doko at cs dot tu-berlin dot de 2004-03-09 18:32 ` jtv at xs4all dot nl 2004-03-09 19:32 ` phil at jaj dot com [this message] 2004-03-09 19:48 ` pme at gcc dot gnu dot org 2004-03-09 20:14 ` Zack Weinberg 2004-03-09 20:14 ` zack at codesourcery dot com 2004-03-10 1:12 ` giovannibajo at libero dot it 2004-03-11 7:35 ` pme at gcc dot gnu dot org 2004-03-11 10:05 ` gdr at integrable-solutions dot net 2004-03-11 15:51 ` bangerth at dealii dot org 2004-03-11 15:52 ` bangerth at dealii 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=20040309193214.14091.qmail@sources.redhat.com \ --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: linkBe 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).