Re: PQmakeEmptyPQresult makes my application dumps core?

From: Gregory Stark <stark(at)enterprisedb(dot)com>
To: "Tom Lane" <tgl(at)sss(dot)pgh(dot)pa(dot)us>
Cc: <wooh(at)wooh(dot)hu>, <pgsql-bugs(at)postgresql(dot)org>
Subject: Re: PQmakeEmptyPQresult makes my application dumps core?
Date: 2007-10-10 17:10:41
Message-ID: 87zlyq99pq.fsf@oxford.xeocode.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-bugs

"Tom Lane" <tgl(at)sss(dot)pgh(dot)pa(dot)us> writes:

> Adam PAPAI <wooh(at)wooh(dot)hu> writes:
>> Usually our program dumps core several times a day, but the reason is
>> unknown. All I know from the core file is the lines below.
>
> That failure is inside malloc, not PQmakeEmptyPQresult, and the odds
> are extremely high that the reason is some part of your program
> clobbering memory that doesn't belong to it (and thereby damaging
> malloc's internal data structures). Try running your program under
> Electric Fence or some other debugging malloc package.

Incidentally glic comes with such a debugging malloc which you can get by
defining the environment variable MALLOC_CHECK_ before starting your program.

In bash you can do this by running your program with something like:

MALLOC_CHECK_=3 ./myprogram

--
Gregory Stark
EnterpriseDB http://www.enterprisedb.com

In response to

Browse pgsql-bugs by date

  From Date Subject
Next Message Jon Roberts 2007-10-10 17:14:42 BUG #3667: Job scheduling with Greenplum fails
Previous Message Tom Lane 2007-10-10 13:58:00 Re: BUG #3665: INSERT is not allowed in a non-volatile function