[Date Prev][Date Next] [Thread Prev][Thread Next] [Date Index] [Thread Index]

Re: bb segfault - will someone please confirm?



On Tue, Apr 12, 2005 at 05:43:19PM -0400, Lennart Sorensen wrote:
> On Tue, Apr 12, 2005 at 05:14:09PM -0400, Lennart Sorensen wrote:
> > Yes I get a segfault running with the default options here too.
> > 
> > Maybe I will investigate... :)
> 
> Well here is what gdb returns:
> 
> Program received signal SIGSEGV, Segmentation fault.
> [Switching to Thread 46912510027664 (LWP 24275)]
> 0x00002aaaab520fad in mallopt () from /lib/libc.so.6
> (gdb) where
> #0  0x00002aaaab520fad in mallopt () from /lib/libc.so.6
> #1  0x00002aaaab51ff77 in malloc () from /lib/libc.so.6 
> #2  0x00000000004053d3 in decompressimg (image=0x52c9a0) at image.c:171
> #3  0x00000000004050db in scale (image=0x52c9a0, x1=-31, y1=33554432, x2=238,
>     y2=41425) at image.c:87
> #4  0x000000000040875a in vezen (i1=0x528d80, i2=0x52c9a0, i3=0x530100,     
>     i4=0x533580) at scene1.c:323
> #5  0x0000000000402c5e in bb () at bb.c:342
> #6  0x0000000000405f20 in main (argc=1431568913, argv=0x4) at main.c:202
> (gdb) 
> 
> If you run it with the argument '2' it will start at stage 2 getting you
> to the problem very quickly (5th call to decompressimg has the problem).

Turns out it is a memory wipe caused elsewhere in the program as far as
I can tell.

If you fix this bug, it seems to run perfectly all the way through:

tex.c line 95:
Was: memset(zbuff, 0x55, (X_s * Y_s * sizeof(long)));
Should be: memset(zbuff, 0x55, (X_s * Y_s * sizeof(int)));

Len Sorensen



Reply to: