🚀 go-pugleaf

During debugging of a c++ program compiled on gcc-2.4.5 using gdb-4.9,
I have been encountering the most odd series of errors. These being
segmentation errors caused by __builtin_new having the most incredibly
large size parameter ( if I am reading the gdb output correctly. )

I am not using the builtin String librry as yet. I will be trying this.

It should also be noted, that the same error is also produced by exit()
when called. The value of sz in __builtin_new is always the same,
regardless of where is comes from.

The output from gdb is as follows.


Program received signal 11,  some you must use "\" before leading whitespace
to be printed or after trailing whitespace.
0xf7734634 in malloc ()
(gdb) where
#0  0xf7734634 in malloc ()
#1  0x1c390 in __builtin_new (sz=146568)
#2  0x3f14 in __rs__FR7istreamR6String (is=@0xf7fff884, s=@0xf7fff848)
    at String.cxx:395
#3  0x52c4 in nextword__FR7istreamR7ostreamR6StringRiT3 (infile=@0xf7fff884,
    incfile=@0xf7fff85c, line=@0xf7fff848, pos=@0xf7fff7c8, copy=@0xf7fff798)
    at input.cxx:42
#4  0x6088 in parse__FR7istreamR7ostreamR6StringRt4List1Z9animationRi (
    infile=@0xf7fff884, incfile=@0xf7fff85c, line=@0xf7fff848,
    animl=@0xf7fff940, animid=@0xf7fff854) at input.cxx:103
#5  0x76dc in getinput__FR6StringT0Rt4List1Z9animation (
    infilename=@0xf7fff968, incfilename=@0xf7fff958, animl=@0xf7fff940)
    at input.cxx:260
#6  0x9c74 in main (argc=5, argv=0xf7fffa14) at aniray.cxx:35

     Please could someone email me with any constructive suggestions as to
why these segmentation error are coming. 
     Thanx,
 
     Clint Redwood
     (cabr@eee.nott.ac.uk)