[GRASS5] SegFault in Vect_New_line_struct()

David D Gray ddgray at armadce.demon.co.uk
Wed Jul 26 11:13:10 EDT 2000


spijker at geo.uu.nl wrote:
> 
> Hello all,
> 
> When I try to read a soil usage map, with m.in.e00, in e00 format (size
> +/-15Mb) the only result is a nice core dump. It's hard to read the soil
> usage from that ;-)
> 
> The Segfault occurs after updating 5600 lines in dig_att. When calling
> Vect_new_line_struct() and Vect__new_line_struct() it bombs immediatly
> at the malloc routine in Vect__new_line_struct(). I tried to test the
> malloc return value (void*) but that was of no use, it seems that it
> segfaults before returning anything. I'd like to solve this, and read my
> map, but I don't have any idea where to look. Does anyone have tips?
> 
> The system is a Pentium processor and 128Mb mem (256 swap) running SuSE
> 6.2
> 
> Regards
>         Job Spijker
> 

Hi

Almost always an unexpected bomb-out in malloc() or free() is the result
of a delayed memory allocation problem. So, not likely anything to do
with Vect__new_line_struct().

A likely candidate is m.in.e00/vector.c lines 107, 109, ..., where the
x,y arrays overflow by 1 * sizeof(double). 

David

---------------------------------------- 
If you want to unsubscribe from GRASS Development Team mailing list write to:
minordomo at geog.uni-hannover.de with
subject 'unsubscribe grass5'



More information about the grass-dev mailing list