public inbox for gcc-bugs@sourceware.org help / color / mirror / Atom feed
From: "koliasvskj at gmail dot com" <gcc-bugzilla@gcc.gnu.org> To: gcc-bugs@gcc.gnu.org Subject: [Bug c++/53127] New: cc1plus segmentation fault Date: Thu, 26 Apr 2012 12:32:00 -0000 [thread overview] Message-ID: <bug-53127-4@http.gcc.gnu.org/bugzilla/> (raw) http://gcc.gnu.org/bugzilla/show_bug.cgi?id=53127 Bug #: 53127 Summary: cc1plus segmentation fault Classification: Unclassified Product: gcc Version: 4.6.3 Status: UNCONFIRMED Severity: normal Priority: P3 Component: c++ AssignedTo: unassigned@gcc.gnu.org ReportedBy: koliasvskj@gmail.com Trying to compile project which uses Boost "Meta State Machine" with GCC-4.6.3 on 64bit Slackware (preprocessed file attached). Tried also GCC-4.5.2 (Slackware 64bit and 32bit); the segfault reproduces. Compiled with command: g++ -v -c NodeMgmtService.cpp -o NodeMgmtService.o Resulting output: Reading specs from /usr/lib64/gcc/x86_64-slackware-linux/4.6.3/specs COLLECT_GCC=g++ COLLECT_LTO_WRAPPER=/usr/libexec/gcc/x86_64-slackware-linux/4.6.3/lto-wrapper Target: x86_64-slackware-linux Configured with: ../gcc-4.6.3/configure --prefix=/usr --libdir=/usr/lib64 --mandir=/usr/man --infodir=/usr/info --enable-shared --enable-bootstrap --enable-languages=ada,c,c++,fortran,java,objc,lto --enable-threads=posix --enable-checking=release --with-system-zlib --with-python-dir=/lib64/python2.6/site-packages --disable-libunwind-exceptions --enable-__cxa_atexit --enable-libssp --enable-lto --with-gnu-ld --verbose --disable-multilib --target=x86_64-slackware-linux --build=x86_64-slackware-linux --host=x86_64-slackware-linux Thread model: posix gcc version 4.6.3 (GCC) COLLECT_GCC_OPTIONS='-fexceptions' '-O2' '-v' '-c' '-o' 'NodeMgmtService.o' '-shared-libgcc' '-mtune=generic' '-march=x86-64' /usr/libexec/gcc/x86_64-slackware-linux/4.6.3/cc1plus -quiet -v -D_GNU_SOURCE NodeMgmtService.cpp -quiet -dumpbase NodeMgmtService.cpp -mtune=generic -march=x86-64 -auxbase-strip NodeMgmtService.o -O2 -version -fexceptions -o /tmp/ccAUJVem.s GNU C++ (GCC) version 4.6.3 (x86_64-slackware-linux) compiled by GNU C version 4.6.3, GMP version 5.0.1, MPFR version 3.0.1, MPC version 0.8.2 GGC heuristics: --param ggc-min-expand=100 --param ggc-min-heapsize=131072 ignoring duplicate directory "/usr/lib64/qt/include" ignoring nonexistent directory "/usr/lib64/gcc/x86_64-slackware-linux/4.6.3/../../../../x86_64-slackware-linux/include" #include "..." search starts here: #include <...> search starts here: /usr/lib64/qt/include /usr/lib64/gcc/x86_64-slackware-linux/4.6.3/../../../../include/c++/4.6.3 /usr/lib64/gcc/x86_64-slackware-linux/4.6.3/../../../../include/c++/4.6.3/x86_64-slackware-linux /usr/lib64/gcc/x86_64-slackware-linux/4.6.3/../../../../include/c++/4.6.3/backward /usr/lib64/gcc/x86_64-slackware-linux/4.6.3/include /usr/local/include /usr/lib64/gcc/x86_64-slackware-linux/4.6.3/include-fixed /usr/include End of search list. GNU C++ (GCC) version 4.6.3 (x86_64-slackware-linux) compiled by GNU C version 4.6.3, GMP version 5.0.1, MPFR version 3.0.1, MPC version 0.8.2 GGC heuristics: --param ggc-min-expand=100 --param ggc-min-heapsize=131072 Compiler executable checksum: f532930d3a80fa20ce9d2d111bdd13e3 g++: internal compiler error: Segmentation fault (program cc1plus) Please submit a full bug report, with preprocessed source if appropriate. See <http://gcc.gnu.org/bugs.html> for instructions.
next reply other threads:[~2012-04-26 12:32 UTC|newest] Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top 2012-04-26 12:32 koliasvskj at gmail dot com [this message] 2012-04-26 13:00 ` [Bug c++/53127] " koliasvskj at gmail dot com 2012-04-26 13:13 ` manu at gcc dot gnu.org 2012-04-26 13:47 ` rguenth at gcc dot gnu.org 2012-10-11 22:39 ` paolo.carlini at oracle dot com 2012-10-12 7:52 ` rguenth 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-53127-4@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).