From stdcxx-dev-return-6332-apmail-incubator-stdcxx-dev-archive=incubator.apache.org@incubator.apache.org Sun Dec 02 23:38:15 2007 Return-Path: Delivered-To: apmail-incubator-stdcxx-dev-archive@www.apache.org Received: (qmail 5990 invoked from network); 2 Dec 2007 23:38:15 -0000 Received: from hermes.apache.org (HELO mail.apache.org) (140.211.11.2) by minotaur.apache.org with SMTP; 2 Dec 2007 23:38:15 -0000 Received: (qmail 25304 invoked by uid 500); 2 Dec 2007 23:38:03 -0000 Delivered-To: apmail-incubator-stdcxx-dev-archive@incubator.apache.org Received: (qmail 25293 invoked by uid 500); 2 Dec 2007 23:38:03 -0000 Mailing-List: contact stdcxx-dev-help@incubator.apache.org; run by ezmlm Precedence: bulk List-Help: List-Unsubscribe: List-Post: List-Id: Reply-To: stdcxx-dev@incubator.apache.org Delivered-To: mailing list stdcxx-dev@incubator.apache.org Received: (qmail 25282 invoked by uid 99); 2 Dec 2007 23:38:03 -0000 Received: from athena.apache.org (HELO athena.apache.org) (140.211.11.136) by apache.org (qpsmtpd/0.29) with ESMTP; Sun, 02 Dec 2007 15:38:03 -0800 X-ASF-Spam-Status: No, hits=-100.0 required=10.0 tests=ALL_TRUSTED X-Spam-Check-By: apache.org Received: from [140.211.11.4] (HELO brutus.apache.org) (140.211.11.4) by apache.org (qpsmtpd/0.29) with ESMTP; Sun, 02 Dec 2007 23:37:40 +0000 Received: from brutus (localhost [127.0.0.1]) by brutus.apache.org (Postfix) with ESMTP id 3487F714201 for ; Sun, 2 Dec 2007 15:37:43 -0800 (PST) Message-ID: <4104888.1196638663212.JavaMail.jira@brutus> Date: Sun, 2 Dec 2007 15:37:43 -0800 (PST) From: "Martin Sebor (JIRA)" To: stdcxx-dev@incubator.apache.org Subject: [jira] Commented: (STDCXX-229) better exception error messages In-Reply-To: <31692844.1151519789913.JavaMail.jira@brutus> MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: 7bit X-Virus-Checked: Checked by ClamAV on apache.org [ https://issues.apache.org/jira/browse/STDCXX-229?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12547692 ] Martin Sebor commented on STDCXX-229: ------------------------------------- A common request is to add the stack trace at the call site to the exception what() string. See, for example, the following gcc enhancement request: http://gcc.gnu.org/bugzilla/show_bug.cgi?id=33903 > better exception error messages > ------------------------------- > > Key: STDCXX-229 > URL: https://issues.apache.org/jira/browse/STDCXX-229 > Project: C++ Standard Library > Issue Type: Improvement > Components: 18. Language Support, 19. Diagnostics > Affects Versions: 4.1.2, 4.1.3, 4.1.4, 4.2.0 > Environment: all > Reporter: Martin Sebor > Fix For: 4.3 > > > ****Created By: sebor @ Apr 24, 2001 12:11:59 PM**** > Subject: better exception error messages (by using CRTL's strerror()?) (1601) > Date: Tue, 24 Apr 2001 10:57:13 -0400 > From: cxxrtl@cxxc.zko.dec.com > To: OEMSUPPORT@roguewave.com > A customer requested that the what() string for a standard iostream > error be more descriptive, possibly by using the strerror() or > perror() function to return the underlying CRTL error string... > Example: > #define __USE_STD_IOSTREAM > #include > #include > int main() { > try { > std::ofstream out; > out.exceptions(std::ios_base::badbit); > out.open("#3.2_BLUE_%.LinkedText"); > out << "Hello!" << std::endl; > } > catch (std::exception& e) { > perror("The funny looking name that isn't in scope anymore"); > std::cerr << e.what(); > } > } > ------------------------------- test.cxx ------------------------------- > $ run test > The funny looking name that isn't in scope anymore: non-translatable vms > error code: 0x186D4 %rms-f-syn, file specification syntax error > iostream object has failbit set > ****Modified By: sebor @ Sep 29, 2003 11:44:10 AM**** > This would be quite useful but it's non trivial to do in iostreams where exceptions are thrown from stream classes but errors of interest typically occur in stream buffers. Once possibility is to selectively capture and save errno in a thread-safe way (so that it can be later modified w/o affecting the recorded cause of the original error) when it occurs during libc and system calls made from streambuf members and later retrieve it when an exception is about to be thrown from the stream class. -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.