public inbox for gcc-bugs@sourceware.org help / color / mirror / Atom feed
From: "pcarlini at suse dot de" <gcc-bugzilla@gcc.gnu.org> To: gcc-bugs@gcc.gnu.org Subject: [Bug libstdc++/21271] Invalid free in std::string Date: Thu, 28 Apr 2005 21:57:00 -0000 [thread overview] Message-ID: <20050428215752.26323.qmail@sourceware.org> (raw) In-Reply-To: <20050428210321.21271.chris@bubblescope.net> ------- Additional Comments From pcarlini at suse dot de 2005-04-28 21:57 ------- Hi Chris. Whereas I'm not seeing anything wrong with Valgrind on x86, I'm willing to check also ppc-darwin but would appreciate detailed instructions to reproduce the problem. In the meanwhile, I would suggest checking whether is an artifact due to the pool allocation of mt_alloc: can you repeat your test with a GCC built with --enable-libstdcxx-allocator=new?!? -- What |Removed |Added ---------------------------------------------------------------------------- Status|UNCONFIRMED |WAITING http://gcc.gnu.org/bugzilla/show_bug.cgi?id=21271
next prev parent reply other threads:[~2005-04-28 21:57 UTC|newest] Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top 2005-04-28 21:03 [Bug libstdc++/21271] New: " chris at bubblescope dot net 2005-04-28 21:57 ` pcarlini at suse dot de [this message] 2005-05-01 10:08 ` [Bug libstdc++/21271] " chris at bubblescope dot net
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=20050428215752.26323.qmail@sourceware.org \ --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).