Skip site navigation (1)
Skip section navigation (2)
Peripheral Links
Header And Logo
|
Site Navigation
Re: E_BAD_ACCESS with palloc/pfree in base type
- From: Gregory Stark <stark(at)enterprisedb(dot)com>
- To: "Michael Glaesemann" <grzm(at)seespotcode(dot)net>
- Cc: "pgsql-general" <pgsql-general(at)postgresql(dot)org>
- Subject: Re: E_BAD_ACCESS with palloc/pfree in base type
- Date: Fri, 31 Aug 2007 09:02:03 +0100
"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. I wonder how you define XTypeMaximumStringLength as sizeof(<integer constant>) ought to give a compile-time error. -- Gregory Stark EnterpriseDB http://www.enterprisedb.com
- Follow-Ups:
- Re: E_BAD_ACCESS with palloc/pfree in base type
- From: Michael Glaesemann
- Re: E_BAD_ACCESS with palloc/pfree in base type
- References:
- E_BAD_ACCESS with palloc/pfree in base type
- From: Michael Glaesemann
- E_BAD_ACCESS with palloc/pfree in base type
- Prev by Date: Re: ERROR: table row type and query-specified row type do not match
- Next by Date: Query the catalog
- Previous by thread: E_BAD_ACCESS with palloc/pfree in base type
- Next by thread: Re: E_BAD_ACCESS with palloc/pfree in base type
- Indexes: