public inbox for gcc-prs@sourceware.org
help / color / mirror / Atom feed
* Re: libstdc++/2921
@ 2001-05-26 20:26 Phil Edwards
  0 siblings, 0 replies; 3+ messages in thread
From: Phil Edwards @ 2001-05-26 20:26 UTC (permalink / raw)
  To: nobody; +Cc: gcc-prs

The following reply was made to PR libstdc++/2921; it has been noted by GNATS.

From: Phil Edwards <pedwards@disaster.jaj.com>
To: Petter Reinholdtsen <pere@hungry.com>
Cc: gcc-gnats@gcc.gnu.org
Subject: Re: libstdc++/2921
Date: Sat, 26 May 2001 22:05:11 -0400

 On Sat, May 26, 2001 at 05:56:01PM -0000, Petter Reinholdtsen wrote:
 >  Thanks for the suggestion on libstdc++-v3.  I tested the GCC online commpiler
 >  and got this result with build 2001-05-26:
 >  
 >    Catched: St9exception
 >    Catched: St9bad_alloc
 >  
 >  At least this time the output is consistent, but I think
 >  'std::exception' and 'std::bad_alloc' would be better choices. :-)
 
 You're seeing the mangled names.  In theory, if you ran those names through
 the demangler (c++filt), you'd see the "human" names.
 
 In practice, as of today, those aren't what c++filt is looking for, so
 the demangler doesn't demangle them.  The names themselves are correct,
 but they're missing the 'local prefix':
 
     % echo St9exception | ~/build/install-2001-05-25-3branch/bin/c++filt
     St9exception
     % echo _ZSt9exception | ~/build/install-2001-05-25-3branch/bin/c++filt
     std::exception
 
 
 Phil
 
 -- 
 pedwards at disaster dot jaj dot com  |  pme at sources dot redhat dot com
 devphil at several other less interesting addresses in various dot domains
 The gods do not protect fools.  Fools are protected by more capable fools.


^ permalink raw reply	[flat|nested] 3+ messages in thread

* Re: libstdc++/2921
@ 2001-05-26 10:56 Petter Reinholdtsen
  0 siblings, 0 replies; 3+ messages in thread
From: Petter Reinholdtsen @ 2001-05-26 10:56 UTC (permalink / raw)
  To: nobody; +Cc: gcc-prs

The following reply was made to PR libstdc++/2921; it has been noted by GNATS.

From: Petter Reinholdtsen <pere@hungry.com>
To: gcc-gnats@gcc.gnu.org
Cc:  
Subject: Re: libstdc++/2921
Date: Sat, 26 May 2001 19:51:22 +0200

 Thanks for the suggestion on libstdc++-v3.  I tested the GCC online commpiler
 and got this result with build 2001-05-26:
 
   Catched: St9exception
   Catched: St9bad_alloc
 
 At least this time the output is consistent, but I think
 'std::exception' and 'std::bad_alloc' would be better choices. :-)


^ permalink raw reply	[flat|nested] 3+ messages in thread

* Re: libstdc++/2921
@ 2001-05-25 15:36 bkoz
  0 siblings, 0 replies; 3+ messages in thread
From: bkoz @ 2001-05-25 15:36 UTC (permalink / raw)
  To: nobody; +Cc: gcc-prs

The following reply was made to PR libstdc++/2921; it has been noted by GNATS.

From: bkoz@gcc.gnu.org
To: gcc-gnats@gcc.gnu.org, nobody@gcc.gnu.org, pere@hungry.com
Cc:  
Subject: Re: libstdc++/2921
Date: 25 May 2001 22:29:15 -0000

 Synopsis: exception::what() return '9exception', not 'exception'
 
 State-Changed-From-To: open->analyzed
 State-Changed-By: bkoz
 State-Changed-When: Fri May 25 15:29:15 2001
 State-Changed-Why:
     This was reported against libstdc++-v2, and this bug report database if for libstdc++-v3.
     
     Note that the string returned by std::exception::what() is implementation defined, so '9exception' is certainly ok. 
     
     In anycase, I think somebody should go over the v3 code and make sure that when exceptions are thrown, the string/message thrown is somewhat consistent. 
 
 http://gcc.gnu.org/cgi-bin/gnatsweb.pl?cmd=view&pr=2921&database=gcc


^ permalink raw reply	[flat|nested] 3+ messages in thread

end of thread, other threads:[~2001-05-26 20:26 UTC | newest]

Thread overview: 3+ messages (download: mbox.gz / follow: Atom feed)
-- links below jump to the message on this page --
2001-05-26 20:26 libstdc++/2921 Phil Edwards
  -- strict thread matches above, loose matches on Subject: below --
2001-05-26 10:56 libstdc++/2921 Petter Reinholdtsen
2001-05-25 15:36 libstdc++/2921 bkoz

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).