Postgres Pro
Downloads
Home   >   mailing lists

Thread: Double Free or corruption

Double Free or corruption

From
Ishaya Bhatt
Date:
Hi,
     Does anyone have any idea what is the cause for the below error:


*** glibc detected *** postgres: ishaya mydb [local] SELECT: double free or corruption (!prev): 0x00000000026bc710 ***

I am modifying code of sorting query, but instead of the required output, this error is thrown in the logs.

Re: Double Free or corruption

From
Payal Singh
Date:
Which OS and postgres version are you using?

Payal Singh,
OmniTi Computer Consulting Inc.
Junior Database Architect,
Phone: 240.646.0770 x 253


On Wed, Oct 30, 2013 at 5:53 AM, Ishaya Bhatt <ishayabhatt@gmail.com> wrote:
Hi,
     Does anyone have any idea what is the cause for the below error:


*** glibc detected *** postgres: ishaya mydb [local] SELECT: double free or corruption (!prev): 0x00000000026bc710 ***

I am modifying code of sorting query, but instead of the required output, this error is thrown in the logs.

Re: Double Free or corruption

From
Amol Bhangdiya
Date:
Hi Ishaya,

Are you using palloc and pfree for memory management?
If not then it should be the correct way to allocate memory in postgreSQL

Regards,
Amol Bhangdiya


On Wed, Oct 30, 2013 at 9:09 PM, Payal Singh <payal@omniti.com> wrote:
Which OS and postgres version are you using?

Payal Singh,
OmniTi Computer Consulting Inc.
Junior Database Architect,
Phone: 240.646.0770 x 253


On Wed, Oct 30, 2013 at 5:53 AM, Ishaya Bhatt <ishayabhatt@gmail.com> wrote:
Hi,
     Does anyone have any idea what is the cause for the below error:


*** glibc detected *** postgres: ishaya mydb [local] SELECT: double free or corruption (!prev): 0x00000000026bc710 ***

I am modifying code of sorting query, but instead of the required output, this error is thrown in the logs.


Re: Double Free or corruption

From
Amol Bhangdiya
Date:
Hi Ishaya,

Are you using palloc and pfree for memory management?
If not then it should be the correct way to allocate memory in postgreSQL

Regards,
Amol Bhangdiya

   



On Wednesday, 30 October 2013 3:24 PM, Ishaya Bhatt <ishayabhatt@gmail.com> wrote:
Hi,
     Does anyone have any idea what is the cause for the below error:


*** glibc detected *** postgres: ishaya mydb [local] SELECT: double free or corruption (!prev): 0x00000000026bc710 ***

I am modifying code of sorting query, but instead of the required output, this error is thrown in the logs.


Re: Double Free or corruption

From
Ishaya Bhatt
Date:
I am using Ubuntu 12.04 and PostGreSQL 9.2.4.


On Thu, Oct 31, 2013 at 12:18 AM, Amol Bhangdiya <amol.b89@gmail.com> wrote:
Hi Ishaya,

Are you using palloc and pfree for memory management?
If not then it should be the correct way to allocate memory in postgreSQL

Regards,
Amol Bhangdiya


On Wed, Oct 30, 2013 at 9:09 PM, Payal Singh <payal@omniti.com> wrote:
Which OS and postgres version are you using?

Payal Singh,
OmniTi Computer Consulting Inc.
Junior Database Architect,
Phone: 240.646.0770 x 253


On Wed, Oct 30, 2013 at 5:53 AM, Ishaya Bhatt <ishayabhatt@gmail.com> wrote:
Hi,
     Does anyone have any idea what is the cause for the below error:


*** glibc detected *** postgres: ishaya mydb [local] SELECT: double free or corruption (!prev): 0x00000000026bc710 ***

I am modifying code of sorting query, but instead of the required output, this error is thrown in the logs.



Re: Double Free or corruption

From
Albe Laurenz
Date:
Ishaya Bhatt wrote:
>      Does anyone have any idea what is the cause for the below error:
> 
> 
> *** glibc detected *** postgres: ishaya mydb [local] SELECT: double free or corruption (!prev):
> 0x00000000026bc710 ***
> 
> 
> I am modifying code of sorting query, but instead of the required output, this error is thrown in the
> logs.

To debug problems like this, I usually use "valgrind".

Yours,
Laurenz Albe