public inbox for gcc-bugs@sourceware.org help / color / mirror / Atom feed
From: "ehrhardt at mathematik dot uni-ulm dot de" <gcc-bugzilla@gcc.gnu.org> To: gcc-bugs@gcc.gnu.org Subject: [Bug libstdc++/11584] ios::iword() fails to zero-initialize storage on failure Date: Tue, 29 Jul 2003 16:56:00 -0000 [thread overview] Message-ID: <20030729165657.31999.qmail@sources.redhat.com> (raw) In-Reply-To: <20030718231013.11584.sebor@roguewave.com> PLEASE REPLY TO gcc-bugzilla@gcc.gnu.org ONLY, *NOT* gcc-bugs@gcc.gnu.org. http://gcc.gnu.org/bugzilla/show_bug.cgi?id=11584 ehrhardt at mathematik dot uni-ulm dot de changed: What |Removed |Added ---------------------------------------------------------------------------- Status|UNCONFIRMED |NEW Ever Confirmed| |1 Last reconfirmed|0000-00-00 00:00:00 |2003-07-29 16:56:56 date| | Version|3.2 |3.3 ------- Additional Comments From ehrhardt at mathematik dot uni-ulm dot de 2003-07-29 16:56 ------- I think I can confirm this. 27.4.2.5 states about the iword function: | Returns: On success iarray[ idx]. On failure, a valid long& | initialized to 0. Currently _M_grow_words returns a reference to _M_word_zero which is initially set to zero but there is no guarantee that this continues to be the case. The solution is to set _M_word_zero to 0 in _M_grow_words before returning a reference to it. This is ok because p2 states: | The reference returned may become invalid after another call to the | object's iword member with a different index, after a call to its | copyfmt member, or when the object is destroyed. I'll attach a proposed patch that should fix this. However, I can't regtest 3.4 at the moment due to libiconv Problems with the testsuite.
next prev parent reply other threads:[~2003-07-29 16:56 UTC|newest] Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top 2003-07-18 23:10 [Bug libstdc++/11584] New: " sebor at roguewave dot com 2003-07-29 16:56 ` ehrhardt at mathematik dot uni-ulm dot de [this message] 2003-08-23 0:52 ` [Bug libstdc++/11584] " dhazeghi at yahoo dot com 2003-09-10 14:46 ` bkoz at gcc dot gnu dot org 2003-09-17 23:50 ` bkoz at gcc dot gnu dot org 2003-09-18 12:35 ` Christian Ehrhardt 2003-09-18 12:49 ` ehrhardt at mathematik dot uni-ulm dot de 2003-12-30 20:42 ` jlquinn at optonline dot net 2004-01-08 17:21 ` bkoz at gcc dot gnu dot org 2004-01-26 1:45 ` jlquinn at gcc dot gnu dot org 2004-01-26 20:36 ` bkoz at redhat dot com 2004-01-27 2:32 ` jlquinn at gcc dot gnu dot org 2004-01-27 2:33 ` jlquinn at gcc dot gnu dot org 2004-01-27 4:50 ` bkoz at redhat dot com 2004-01-27 15:46 ` cvs-commit at gcc dot gnu dot org 2004-01-27 15:54 ` cvs-commit at gcc dot gnu dot org 2004-01-27 15:55 ` jlquinn at gcc dot gnu dot org 2004-01-27 16:00 ` pinskia at gcc dot gnu dot org
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=20030729165657.31999.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).