public inbox for gcc-bugs@sourceware.org help / color / mirror / Atom feed
From: "costamagnagianfranco at yahoo dot it" <gcc-bugzilla@gcc.gnu.org> To: gcc-bugs@gcc.gnu.org Subject: [Bug libstdc++/66262] [REGRESSION] testsuite failure with libstdc++ (gcc-5) and g++-4.9 together Date: Mon, 01 Jun 2015 09:51:00 -0000 [thread overview] Message-ID: <bug-66262-4-NAgX6bXkbT@http.gcc.gnu.org/bugzilla/> (raw) In-Reply-To: <bug-66262-4@http.gcc.gnu.org/bugzilla/> https://gcc.gnu.org/bugzilla/show_bug.cgi?id=66262 --- Comment #6 from Gianfranco <costamagnagianfranco at yahoo dot it> --- Created attachment 35662 --> https://gcc.gnu.org/bugzilla/attachment.cgi?id=35662&action=edit "Reduced" testcase I tried in the last few days to reduce as much as possible the testcase. I really hope it is enough for you to understand something more :) to reproduce: pbuilder-dist sid create pbuilder-dist sid login apt-get install vim cmake apt-get install libboost-chrono-dev libboost-system-dev libboost-locale-dev libboost-filesystem-dev apt-get install g++-5 cd casablanca/ mkdir build cd build/ cmake .. && make test_runner streams_test -j 9 && cd Binaries/ && ./test_runner libstreams_test.so #FAILURE cd ../.. mkdir build-gcc5 cd build-gcc5 export CXX=g++-5 cmake .. && make test_runner streams_test -j 9 && cd Binaries/ && ./test_runner libstreams_test.so #SUCCESS the build needs unittestpp to create the unittest, and needs the "test_runner" to open the library .so to run tests inside. The bug is for sure in the libstreams_test.so, created from this source file tests/functional/streams/fstreambuf_tests.cpp I guess this because copying the .so built in gcc-5 directory in the gcc-4 one makes the testsuite pass the tests. I can provide the binaries if needed, unfortunately I don't know how to debug the library inside, since it is called with dlopen. g++ -v Using built-in specs. COLLECT_GCC=g++ COLLECT_LTO_WRAPPER=/usr/lib/gcc/x86_64-linux-gnu/4.9/lto-wrapper Target: x86_64-linux-gnu Configured with: ../src/configure -v --with-pkgversion='Debian 4.9.2-19' --with-bugurl=file:///usr/share/doc/gcc-4.9/README.Bugs --enable-languages=c,c++,java,go,d,fortran,objc,obj-c++ --prefix=/usr --program-suffix=-4.9 --enable-shared --enable-linker-build-id --libexecdir=/usr/lib --without-included-gettext --enable-threads=posix --with-gxx-include-dir=/usr/include/c++/4.9 --libdir=/usr/lib --enable-nls --with-sysroot=/ --enable-clocale=gnu --enable-libstdcxx-debug --enable-libstdcxx-time=yes --enable-gnu-unique-object --disable-vtable-verify --enable-plugin --with-system-zlib --disable-browser-plugin --enable-java-awt=gtk --enable-gtk-cairo --with-java-home=/usr/lib/jvm/java-1.5.0-gcj-4.9-amd64/jre --enable-java-home --with-jvm-root-dir=/usr/lib/jvm/java-1.5.0-gcj-4.9-amd64 --with-jvm-jar-dir=/usr/lib/jvm-exports/java-1.5.0-gcj-4.9-amd64 --with-arch-directory=amd64 --with-ecj-jar=/usr/share/java/eclipse-ecj.jar --enable-objc-gc --enable-multiarch --with-arch-32=i586 --with-abi=m64 --with-multilib-list=m32,m64,mx32 --enable-multilib --with-tune=generic --enable-checking=release --build=x86_64-linux-gnu --host=x86_64-linux-gnu --target=x86_64-linux-gnu Thread model: posix gcc version 4.9.2 (Debian 4.9.2-19) g++-5 -v Using built-in specs. COLLECT_GCC=g++-5 COLLECT_LTO_WRAPPER=/usr/lib/gcc/x86_64-linux-gnu/5/lto-wrapper Target: x86_64-linux-gnu Configured with: ../src/configure -v --with-pkgversion='Debian 5.1.1-8' --with-bugurl=file:///usr/share/doc/gcc-5/README.Bugs --enable-languages=c,ada,c++,java,go,d,fortran,objc,obj-c++ --prefix=/usr --program-suffix=-5 --enable-shared --enable-linker-build-id --libexecdir=/usr/lib --without-included-gettext --enable-threads=posix --libdir=/usr/lib --enable-nls --with-sysroot=/ --enable-clocale=gnu --enable-libstdcxx-debug --enable-libstdcxx-time=yes --with-default-libstdcxx-abi=c++98 --disable-libstdcxx-dual-abi --enable-gnu-unique-object --disable-vtable-verify --enable-libmpx --enable-plugin --with-system-zlib --disable-browser-plugin --enable-java-awt=gtk --enable-gtk-cairo --with-java-home=/usr/lib/jvm/java-1.5.0-gcj-5-amd64/jre --enable-java-home --with-jvm-root-dir=/usr/lib/jvm/java-1.5.0-gcj-5-amd64 --with-jvm-jar-dir=/usr/lib/jvm-exports/java-1.5.0-gcj-5-amd64 --with-arch-directory=amd64 --with-ecj-jar=/usr/share/java/eclipse-ecj.jar --enable-objc-gc --enable-multiarch --with-arch-32=i586 --with-abi=m64 --with-multilib-list=m32,m64,mx32 --enable-multilib --with-tune=generic --enable-checking=release --build=x86_64-linux-gnu --host=x86_64-linux-gnu --target=x86_64-linux-gnu Thread model: posix gcc version 5.1.1 20150528 (Debian 5.1.1-8) copying libstdc++6 from an ubuntu machine makes the test successfully pass on the gcc-4 build. (don't know how much of this is helpful for you) thanks a lot, Gianfranco
next prev parent reply other threads:[~2015-06-01 9:51 UTC|newest] Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top 2015-05-23 10:08 [Bug libstdc++/66262] New: " costamagnagianfranco at yahoo dot it 2015-05-23 10:17 ` [Bug libstdc++/66262] " trippels at gcc dot gnu.org 2015-05-23 10:49 ` costamagnagianfranco at yahoo dot it 2015-05-23 10:59 ` trippels at gcc dot gnu.org 2015-05-26 13:44 ` trippels at gcc dot gnu.org 2015-05-26 13:57 ` costamagnagianfranco at yahoo dot it 2015-05-26 13:59 ` costamagnagianfranco at yahoo dot it 2015-06-01 9:51 ` costamagnagianfranco at yahoo dot it [this message] 2015-06-01 10:17 ` trippels at gcc dot gnu.org 2015-06-01 10:30 ` costamagnagianfranco at yahoo dot it 2015-06-01 10:40 ` trippels at gcc dot gnu.org 2015-06-01 11:32 ` doko at gcc dot gnu.org 2015-06-01 12:02 ` hjl.tools at gmail dot com 2015-06-01 12:13 ` redi at gcc dot gnu.org 2015-06-01 12:19 ` redi at gcc dot gnu.org 2015-06-01 12:21 ` redi at gcc dot gnu.org 2015-06-01 12:52 ` costamagnagianfranco at yahoo dot it 2015-06-06 12:17 ` redi at gcc dot gnu.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=bug-66262-4-NAgX6bXkbT@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).