[Bug c++/43818] internal compiler error: Segmentation fault

[oberlaender at fzi dot de]

------- Comment #5 from oberlaender at fzi dot de  2010-04-20 16:51 -------
I don't think it's the memory, I've got 4 GB at my disposal (32-Bit system with
PAE kernel), and it doesn't seem to take up much memory:

$ uname -a
Linux delorean 2.6.31-20-generic-pae #58-Ubuntu SMP Fri Mar 12 06:25:51 UTC
2010 i686 GNU/Linux

$ free
             total       used       free     shared    buffers     cached
Mem:       3921840    2022788    1899052          0     380908    1064988
-/+ buffers/cache:     576892    3344948
Swap:      4294040          0    4294040

$ strace -emmap2,mremap,brk,setrlimit g++ -c -o bugtest.out -O2 bugtest.ii 
brk(0)                                  = 0x97a3000
mmap2(NULL, 8192, PROT_READ|PROT_WRITE, MAP_PRIVATE|MAP_ANONYMOUS, -1, 0) =
0xb781d000
mmap2(NULL, 139729, PROT_READ, MAP_PRIVATE, 3, 0) = 0xb77fa000
mmap2(NULL, 1329512, PROT_READ|PROT_EXEC, MAP_PRIVATE|MAP_DENYWRITE, 3, 0) =
0xb76b5000
mmap2(0xb77f4000, 12288, PROT_READ|PROT_WRITE,
MAP_PRIVATE|MAP_FIXED|MAP_DENYWRITE, 3, 0x13e) = 0xb77f4000
mmap2(0xb77f7000, 10600, PROT_READ|PROT_WRITE,
MAP_PRIVATE|MAP_FIXED|MAP_ANONYMOUS, -1, 0) = 0xb77f7000
mmap2(NULL, 4096, PROT_READ|PROT_WRITE, MAP_PRIVATE|MAP_ANONYMOUS, -1, 0) =
0xb76b4000
brk(0)                                  = 0x97a3000
brk(0x97c4000)                          = 0x97c4000
mmap2(NULL, 1085056, PROT_READ, MAP_PRIVATE, 3, 0) = 0xb75ab000
mmap2(NULL, 4096, PROT_READ|PROT_WRITE, MAP_PRIVATE|MAP_ANONYMOUS, -1, 0) =
0xb781c000
mmap2(NULL, 256316, PROT_READ, MAP_PRIVATE, 3, 0) = 0xb756c000
mmap2(NULL, 26048, PROT_READ, MAP_SHARED, 3, 0) = 0xb7816000
mmap2(NULL, 52, PROT_READ, MAP_PRIVATE, 3, 0) = 0xb7815000
projects/odete/bugtest.cpp: In member function ‘bool
tBspTree2D::Intersect(const tVec2f&, const tVec2f&, tVec2f&, double) const
[with bool oriented = true]Â’:
projects/odete/bugtest.cpp:81: internal compiler error: Segmentation fault
Please submit a full bug report,
with preprocessed source if appropriate.
See <file:///usr/share/doc/gcc-4.4/README.Bugs> for instructions.
--- SIGCHLD (Child exited) @ 0 (0) ---

I've also confirmed the same behavior on another system running the same OS and
gcc version, so my RAM is probably OK.

I'll try it with >=4.4.2 later.


-- 


http://gcc.gnu.org/bugzilla/show_bug.cgi?id=43818