public inbox for gcc-bugs@sourceware.org help / color / mirror / Atom feed
From: "asmwarrior at gmail dot com" <gcc-bugzilla@gcc.gnu.org> To: gcc-bugs@gcc.gnu.org Subject: [Bug c++/56926] Crash (without ICE) while compiling Boost.Math Date: Sat, 28 Dec 2013 09:22:00 -0000 [thread overview] Message-ID: <bug-56926-4-dy5zELhsPr@http.gcc.gnu.org/bugzilla/> (raw) In-Reply-To: <bug-56926-4@http.gcc.gnu.org/bugzilla/> http://gcc.gnu.org/bugzilla/show_bug.cgi?id=56926 --- Comment #6 from asmwarrior <asmwarrior at gmail dot com> --- It is very simple to reproduce this bug. Here is the steps I do 1, download the GCC 4.8.2 from MinGW-w64 site, I'm using i686-4.8.2-release-posix-dwarf-rt_v3-rev1 2, download the boost source package, I'm using boost_1_55_0.7z download from boost official site, extract its source to some folder like: D:\mingw-builds\boost_1_55_0. (Note, no need to build boost library, only the boost header files are needed for testing) 3, create a simple file named "pch.h", which contains following: -------------------- #ifndef pch_h #define pch_h #pragma GCC diagnostic push #pragma GCC diagnostic ignored "-Wdelete-non-virtual-dtor" #include <boost/asio.hpp> #include <boost/iostreams/filtering_stream.hpp> #include <boost/program_options.hpp> #include <boost/thread.hpp> #pragma GCC diagnostic pop #endif -------------------- 4, create a simple "test.cpp" file, which contains following: -------------------- #include "pch.h" int main() { int a; int b; int c; a++; b++; } -------------------- 5, build the pch file by running the command. g++.exe -Wall -fexceptions -g -march=core2 -Wall -ID:\mingw-builds\boost_1_55_0 -c pch.h -o pch.h.gch 6, now, you will see a file named "pch.h.gch" was generated, its size is bigger than 200M. 7, compile the test.cpp file by running the command: g++.exe -v -Wall -fexceptions -g -march=core2 -Wall -ID:\mingw-builds\boost_1_55_0 -Winvalid-pch -include pch.h -c test.cpp -o test.o 8, I see some verbose messages, but no "test.o" file was generated in the working directory, also I see no crash dialog shown. So, this is indeed a bug. Now, if you comment out some lines in the pch.h file, e.g. only leave the first #include directive: #include <boost/asio.hpp>, and comment out the later three include directive, and run the steps again, you get a 47M pch.h.gch and a 206K test.o file. I try to use GDB to catch the errors, but failed. Try use GDB, I did such thing: gdb g++.exe [enter] then set args -v -Wall -fexceptions -g -march=core2 -Wall -ID:\mingw-builds\boost_1_55_0 -Winvalid-pch -include pch.h -c test.cpp -o test.o [enter] then r [enter] GDB can't catch anything, just the same as I run the command in the Command line, the last message from GDB is: [Inferior 1 (process 2000) exited with code 01] Does exit code "01" has some special meaning? BTW: I have test the GCC 4.9 snapshot i686-4.9.0-snapshot-20131119-rev205009-posix-dwarf-rt_v4.7z from mingw-w64 site, it has the same bug.
next prev parent reply other threads:[~2013-12-28 9:22 UTC|newest] Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top 2013-04-11 19:13 [Bug c++/56926] New: " vanboxem.ruben at gmail dot com 2013-04-12 8:42 ` [Bug c++/56926] " rguenth at gcc dot gnu.org 2013-10-15 0:57 ` asmwarrior at gmail dot com 2013-12-27 22:10 ` 1000hz.radiowave at gmail dot com 2013-12-28 9:22 ` asmwarrior at gmail dot com [this message] 2013-12-28 13:42 ` 1000hz.radiowave at gmail dot com 2014-02-26 1:14 ` ai.emma.me at gmail dot com 2014-10-15 22:48 ` andre at netzeband dot eu 2014-11-08 22:00 ` andre at netzeband dot eu 2015-05-20 13:42 ` asmwarrior at gmail dot com 2015-05-22 2:38 ` asmwarrior at gmail dot com 2015-05-22 7:31 ` asmwarrior at gmail dot com 2015-05-31 6:35 ` asmwarrior at gmail dot com 2015-05-31 7:59 ` asmwarrior at gmail dot com 2015-06-02 5:11 ` asmwarrior at gmail dot com 2015-06-02 8:08 ` ismail at donmez dot ws
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-56926-4-dy5zELhsPr@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).