[postgis-devel] Still problems on Ultrasparc with 1.0.5/8.1.0

strk at refractions.net strk at refractions.net
Mon Nov 28 04:14:26 PST 2005

Another thing to try:
All allocations *should* happen through lwalloc() (in liblwgeom.c)
You might trap cases in which size exceeds a threshold and induce
a segfault: free((void *)0x1).
Then run with gdb to see who tried to allocate so much memory.


On Mon, Nov 28, 2005 at 01:07:47PM +0100, Alex Mayrhofer wrote:
> strk at refractions.net wrote:
> >No, GEOS shouldn't have to do with this.
> >The backtrace shows something about index_insert, do
> >dropping index help ?
> I'll try that - however, there's no spatial index defined on the respective 
> table...
> >It would help building postgres with --enable-cassert
> >and -g.
> Will do that.
> cheers
> alex
> _______________________________________________
> postgis-devel mailing list
> postgis-devel at postgis.refractions.net
> http://postgis.refractions.net/mailman/listinfo/postgis-devel


 /"\    ASCII Ribbon Campaign
 \ /    Respect for open standards
  X     No HTML/RTF in email
 / \    No M$ Word docs in email

More information about the postgis-devel mailing list