#1229 internal compiler error: Segmentation fault

Known_bugs
closed
nobody
gcc (462)
2010-08-01
2008-12-29
No

When compiling one of my projects (using and building a dll) I do get this error:
BeleggngFileIO.cpp:5: internal compiler error: Segmentation fault

I managed to build a small example project illustrating the problem.
It is contained in the zip file attached.
Just unzip the files and call the compiler in a cmd prompt:
g++ -I. -c BeleggngFileIO.cpp -o BeleggngFileIO.o

gcc -v reports:

Reading specs from C:/MinGW/Bin/../lib/gcc/mingw32/3.4.5/specs
Configured with: ../gcc-3.4.5-20060117-3/configure --with-gcc --with-gnu-ld --with-gnu-as --host=mingw32 --target=mingw32 --prefix=/mingw --enable-threads --disable-nls --enable-languages=c,c++,f77,ada,objc,java --disable-win32-registry --disable-shared --enable-sjlj-exceptions --enable-libgcj --disable-java-awt --without-x --enable-java-gc=boehm --disable-libgcj-debug --enable-interpreter --enable-hash-synchronization --enable-libstdcxx-debug
Thread model: win32
gcc version 3.4.5 (mingw-vista special r3)

The compiler is run from the windows cmd prompt.
Windows ver reports:
Microsoft Windows 2000 [Version 5.00.2195]

Discussion

  • Test3.zip

     
    Attachments
  • I tried this. (For people who are trying to reproduce this, you probably need to add "path c:\mingw\bin;%path%".) I got an object file, so maybe the bug has been fixed?
    Using built-in specs.
    Target: mingw32
    Configured with: ../gcc-4.4.0/configure --enable-languages=c,ada,c++,fortran,java,objc,obj-c++ --disable-sjlj-exceptions --enable-shared --enable-libgcj --enable-libgomp --with-dwarf2 --disable-win32-registry --enable-libstdcxx-debug --enable-version-specific-runtime-libs --prefix=/mingw --with-gmp=/mingw/src/gmp/root --with-mpfr=/mingw/src/mpfr/root --build=mingw32
    Thread model: win32
    gcc version 4.4.0 (GCC)

     
  • shinobu_maehara,

    I tried to download gcc 4 from sourceforge but unfortunately they still supply gcc 3.4.5.

    Using gcc 3.4.5 I reorganised my code after which the compiler was able to compile the code.

    Assuming you've setup your system well, we can close this issue.

     
  • Could have been solved in gcc 4

     
    • status: open --> closed