public inbox for gcc-bugs@sourceware.org help / color / mirror / Atom feed
From: "myan at microstrategy dot com" <gcc-bugzilla@gcc.gnu.org> To: gcc-bugs@gcc.gnu.org Subject: [Bug c++/34853] New: c++ runtime of basic_string has a bug in certain case Date: Fri, 18 Jan 2008 15:36:00 -0000 [thread overview] Message-ID: <bug-34853-15307@http.gcc.gnu.org/bugzilla/> (raw) The following change in basic_string.tcc is not valid in my usage. A java application loads c++ jni shared library that is compiled with -D_GLIBCXX_FULLY_DYNAMIC_STRING. Please see attached test files. Revision 95358 - (view) (download) - [select for diffs] Modified Mon Feb 21 23:25:08 2005 UTC (2 years, 10 months ago) by paolo Original Path: trunk/libstdc++-v3/include/bits/basic_string.tcc File length: 33828 byte(s) Diff to previous 91466 (colored) 2005-02-21 Paolo Carlini <pcarlini@suse.de> * include/bits/basic_string.tcc (_Rep::_M_destroy): Don't check for this == &_S_empty_rep, it's always false, here. -- Summary: c++ runtime of basic_string has a bug in certain case Product: gcc Version: 4.1.1 Status: UNCONFIRMED Severity: normal Priority: P3 Component: c++ AssignedTo: unassigned at gcc dot gnu dot org ReportedBy: myan at microstrategy dot com http://gcc.gnu.org/bugzilla/show_bug.cgi?id=34853
next reply other threads:[~2008-01-18 15:33 UTC|newest] Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top 2008-01-18 15:36 myan at microstrategy dot com [this message] 2008-01-18 15:36 ` [Bug c++/34853] " myan at microstrategy dot com 2008-01-18 15:48 ` myan at microstrategy dot com 2008-01-18 16:02 ` myan at microstrategy dot com 2008-01-18 16:06 ` myan at microstrategy dot com 2008-01-18 16:08 ` myan at microstrategy dot com 2008-01-19 21:06 ` [Bug libstdc++/34853] " 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=bug-34853-15307@http.gcc.gnu.org/bugzilla/ \ --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).