[postgis-users] Help please

[David Blasby]

Daniel Morissette wrote:
> Sounds very much like a memory issue and you could run after it for days 
> like this.  If you're on Linux then you could install Valgrind 
> (http://developer.kde.org/~sewardj/) and run your request in Valgrind at 
> the command-line.  You'll be amazed by this tool, it should point you in 
> the right direction in a few minutes.  If you're on Windows then you 
> could try Purify from http://www.rational.com/

I've been running the postgis connector in valgrind - I  get these two 
errors::

==12748== Syscall param write(buf) contains uninitialised or 
unaddressable byte(s)
==12748==    at 0x40517384: __libc_write (in /lib/libc-2.2.4.so)
==12748==    by 0x404B1467: (within /lib/libc-2.2.4.so)
==12748==    by 0x404B104A: _IO_do_write (in /lib/libc-2.2.4.so)
==12748==    by 0x404AFE13: _IO_file_close_it (in /lib/libc-2.2.4.so)
==12748==    Address 0x41879035 is not stack'd, malloc'd or free'd

and

==12748== Invalid free() / delete / delete[]
==12748==    at 0x40168E95: free (vg_clientfuncs.c:185)
==12748==    by 0x40551CBC: (within /lib/libc-2.2.4.so)
==12748==    by 0x404BA821: __libc_freeres (in /lib/libc-2.2.4.so)
==12748==    by 0x4016982B: vgPlain___libc_freeres_wrapper 
(vg_clientfuncs.c:590)
==12748==    Address 0x40585308 is not stack'd, malloc'd or free'd


Both of them are not very helpfull since they dont give a full stack 
trace of the offending call.

dave