[postgis-devel] Memory alignment issues (was:crash(somehow)resolved)

Mark Cave-Ayland m.cave-ayland at webbased.co.uk
Fri Nov 18 01:37:07 PST 2005

> -----Original Message-----
> From: postgis-devel-bounces at postgis.refractions.net 
> [mailto:postgis-devel-bounces at postgis.refractions.net] On 
> Behalf Of Michael Fuhr
> Sent: 17 November 2005 23:57
> To: PostGIS Development Discussion
> Subject: Re: [postgis-devel] Memory alignment issues 
> (was:crash(somehow)resolved)


> The crash is due to an assertion in PostgreSQL that's checked 
> only if the server was built with --enable-cassert.  The code is in
> src/backend/utils/mmgr/mcxt.c:
> 161 MemoryContextDelete(MemoryContext context)
> 162 {
> 163     AssertArg(MemoryContextIsValid(context));
> For anybody doing server-side development it's probably a 
> good idea to test on a server built with --enable-cassert; 
> otherwise some problems might go unnoticed.

Hi Michael,

Thanks for getting to this so quickly. You are in fact right - I've been
developing the transform() patch on a different box than normal and of
course, it hadn't been configured with --enable-cassert. I've rebuilt and
applied a fix to CVS for the two SPI warnings and the assertion failure, and
a CVS checkout now works for me with --enabled-cassert under Linux. Please
let me know how you get with the latest CVS.

Kind regards,


WebBased Ltd
17 Research Way

T: +44 (0)1752 797131
F: +44 (0)1752 791023


This email and any attachments are confidential to the intended recipient
and may also be privileged. If you are not the intended recipient please
delete it from your system and notify the sender. You should not copy it or
use it for any purpose nor disclose or distribute its contents to any other

More information about the postgis-devel mailing list