[GRASS5] [bug #4079] (grass) Malloc errors with nviz elev=elevation.dem vect=roads

[Michael Barton]

I always get these too. They don't seem to have any effect on functionality,
but they worry me a bit.

Michael
__________________________________________
Michael Barton, Professor of Anthropology
School of Human Evolution and Social Change
Arizona State University
Tempe, AZ 85287-2402

phone: 480-965-6213
fax: 480-965-7671
www: http://www.public.asu.edu/~cmbarton



> From: Request Tracker <grass-bugs at intevation.de>
> Reply-To: Request Tracker <grass-bugs at intevation.de>
> Date: Sun, 12 Feb 2006 06:34:51 +0100 (CET)
> To: <grass5 at grass.itc.it>
> Subject: [GRASS5] [bug #4079] (grass) Malloc errors with nviz
> elev=elevation.dem vect=roads
> 
> this bug's URL: http://intevation.de/rt/webrt?serial_num=4079
> -------------------------------------------------------------------------
> 
> Subject: Malloc errors with nviz elev=elevation.dem vect=roads
> 
> Platform: Mac OSX
> grass obtained from: Trento Italy site
> grass binary for platform: Downloaded precompiled Binaries
> GRASS Version: Grass-OSX-6.1.cvs-060204.dmg
> 
> Phil Kelly
> I'm new to GRASS and GIS, so take these reports with a grain of salt, but feel
> free to contact me with questions.
> I launched the new install and tried to follow the instructions in the
> neteler_grass6_nutshell2005.pdf.  I chose the spearfish60 dataset, and tried
> to create a new Mapset (with my user id (pwkelly).  Grass appeared to exit
> (which may be another bug).  I quit X11 and relaunched GRASS.  I now saw my
> "pwkelly" in the list with user1 and PERMANENT, and chose it and entered
> GRASS.
> I then entered the NVIZ command shown in the log below.
> 
> Help is available with the command:      g.manual -i
> See the licence terms with:              g.version -c
> If required, restart the graphical user interface with: d.m &
> When ready to quit enter:                exit
> GRASS 6.1.cvs (spearfish60):~ > nviz elev=elevation.dem vect=roads
> Loading Data
> Update elev null mask
> Loading Data
> translating colors
> Vector file roads loaded.
> Total vect memory = 69 Kbytes
> recalculating normals...
> nviz(1182,0xa000ed68) malloc: ***  Deallocation of a pointer not malloced:
> 0x31d
> edc8; This could be a double free(), or free() called with the middle of an
> allo
> cated block; Try setting environment variable MallocHelp to see tools to help
> de
> bug
> nviz(1182,0xa000ed68) malloc: ***  Deallocation of a pointer not malloced:
> 0x31e
> 6c88; This could be a double free(), or free() called with the middle of an
> allo
> cated block; Try setting environment variable MallocHelp to see tools to help
> de
> bug
> nviz(1182,0xa000ed68) malloc: ***  Deallocation of a pointer not malloced:
> 0x31e
> 2f88; This could be a double free(), or free() called with the middle of an
> allo
> cated block; Try setting environment variable MallocHelp to see tools to help
> de
> bug
> nviz(1182,0xa000ed68) malloc: ***  Deallocation of a pointer not malloced:
> 0x32b
> b4c8; This could be a double free(), or free() called with the middle of an
> allo
> cated block; Try setting environment variable MallocHelp to see tools to help
> de
> bug
> nviz(1182,0xa000ed68) malloc: ***  Deallocation of a pointer not malloced:
> 0x33f
> 4708; This could be a double free(), or free() called with the middle of an
> allo
> cated block; Try setting environment variable MallocHelp to see tools to help
> de
> bug
> nviz(1182,0xa000ed68) malloc: ***  Deallocation of a pointer not malloced:
> 0x33f
> 7448; This could be a double free(), or free() called with the middle of an
> allo
> cated block; Try setting environment variable MallocHelp to see tools to help
> de
> bug
> nviz(1182,0xa000ed68) malloc: ***  Deallocation of a pointer not malloced:
> 0x33f
> 76c8; This could be a double free(), or free() called with the middle of an
> allo
> cated block; Try setting environment variable MallocHelp to see tools to help
> de
> bug
> nviz(1182,0xa000ed68) malloc: ***  Deallocation of a pointer not malloced:
> 0x33f
> edc8; This could be a double free(), or free() called with the middle of an
> allo
> cated block; Try setting environment variable MallocHelp to see tools to help
> de
> bug
> % 
> 
> -------------------------------------------- Managed by Request Tracker
> 
> 
>