Re: E_BAD_ACCESS with palloc/pfree in base type

From: Michael Glaesemann <grzm(at)seespotcode(dot)net>
To: Gregory Stark <stark(at)enterprisedb(dot)com>
Cc: "pgsql-general" <pgsql-general(at)postgresql(dot)org>
Subject: Re: E_BAD_ACCESS with palloc/pfree in base type
Date: 2007-08-31 14:52:56
Message-ID: 5023C018-C766-42DB-A9BF-492252B5EF9D@seespotcode.net
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-general


On Aug 31, 2007, at 3:02 , Gregory Stark wrote:

> "Michael Glaesemann" <grzm(at)seespotcode(dot)net> writes:
>
>> char * theDigits = malloc(sizeof(XTypeMaximumStringLength));
> ...
>> char * subscriberNumber = malloc(XTypeMaximumStringLength);
>
> One of those two is wrong, I suspect the first one.

Thanks, Greg. It looks like that was it. Always good to have a fresh
pair of eyes.

> I wonder how you define
> XTypeMaximumStringLength as sizeof(<integer constant>) ought to give a
> compile-time error.

It's an enum value. I do have a few compiler warnings (no errors)
left to clean up, but that doesn't appear to be one of them.

Thanks again for your help!

Michael Glaesemann
grzm seespotcode net

In response to

Browse pgsql-general by date

  From Date Subject
Next Message Tom Lane 2007-08-31 15:07:20 Re: Out of shared memory (locks per process) using table-inheritance style partitioning
Previous Message John Prevost 2007-08-31 14:42:38 Re: Out of shared memory (locks per process) using table-inheritance style partitioning