public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "jmcdonald at fairfield dot com" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug libstdc++/39569] Apparent memory corruption in std::stringstream after calling syslog()
Date: Mon, 30 Mar 2009 14:59:00 -0000 [thread overview]
Message-ID: <20090330145932.27360.qmail@sourceware.org> (raw)
In-Reply-To: <bug-39569-17507@http.gcc.gnu.org/bugzilla/>
------- Comment #4 from jmcdonald at fairfield dot com 2009-03-30 14:59 -------
Created an attachment (id=17560)
--> (http://gcc.gnu.org/bugzilla/attachment.cgi?id=17560&action=view)
The GCC preprocessed files to go with the simple, one-source-file test case.
And here are the gcc preprocessed files that go with the more simple test case.
The gcc -v info from the machine used to produce these is as follows:
Using built-in specs.
Target: x86_64-redhat-linux
Configured with: ../configure --prefix=/usr --mandir=/usr/share/man
--infodir=/usr/share/info --enable-shared --enable-threads=posix
--enable-checking=release --with-system-zlib --enable-__cxa_atexit
--disable-libunwind-exceptions
--enable-languages=c,c++,objc,obj-c++,java,fortran,ada --enable-java-awt=gtk
--disable-dssi --enable-plugin
--with-java-home=/usr/lib/jvm/java-1.5.0-gcj-1.5.0.0/jre
--enable-libgcj-multifile --enable-java-maintainer-mode
--with-ecj-jar=/usr/share/java/eclipse-ecj.jar --with-cpu=generic
--host=x86_64-redhat-linux
Thread model: posix
gcc version 4.1.2 20070925 (Red Hat 4.1.2-33)
Please note, however, that I've been able to reproduce this bug on a new Fedora
10 installation as well... that install's gcc-v is as follows:
Using built-in specs.
Target: i386-redhat-linux
Configured with: ../configure --prefix=/usr --mandir=/usr/share/man
--infodir=/usr/share/info --with-bugurl=http://bugzilla.redhat.com/bugzilla
--enable-bootstrap --enable-shared --enable-threads=posix
--enable-checking=release --with-system-zlib --enable-__cxa_atexit
--disable-libunwind-exceptions
--enable-languages=c,c++,objc,obj-c++,java,fortran,ada --enable-java-awt=gtk
--disable-dssi --enable-plugin
--with-java-home=/usr/lib/jvm/java-1.5.0-gcj-1.5.0.0/jre
--enable-libgcj-multifile --enable-java-maintainer-mode
--with-ecj-jar=/usr/share/java/eclipse-ecj.jar --disable-libjava-multilib
--with-cpu=generic --build=i386-redhat-linux
Thread model: posix
gcc version 4.3.2 20081105 (Red Hat 4.3.2-7) (GCC)
--
jmcdonald at fairfield dot com changed:
What |Removed |Added
----------------------------------------------------------------------------
Attachment #17549|0 |1
is obsolete| |
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=39569
next prev parent reply other threads:[~2009-03-30 14:59 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-03-27 21:53 [Bug libstdc++/39569] New: " jmcdonald at fairfield dot com
2009-03-27 22:00 ` [Bug libstdc++/39569] " jmcdonald at fairfield dot com
2009-03-27 22:06 ` jmcdonald at fairfield dot com
2009-03-30 14:45 ` jmcdonald at fairfield dot com
2009-03-30 14:59 ` jmcdonald at fairfield dot com [this message]
2009-03-30 15:59 ` paolo dot carlini at oracle dot com
2009-03-30 20:56 ` jmcdonald at fairfield dot com
2009-03-30 21:17 ` paolo dot carlini at oracle dot com
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=20090330145932.27360.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: link
Be 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).