Re: PQmakeEmptyPQresult makes my application dumps core? - Mailing list pgsql-bugs

From Gregory Stark
Subject Re: PQmakeEmptyPQresult makes my application dumps core?
Date
Msg-id 87zlyq99pq.fsf@oxford.xeocode.com
Whole thread Raw
In response to Re: PQmakeEmptyPQresult makes my application dumps core?  (Tom Lane <tgl@sss.pgh.pa.us>)
List pgsql-bugs
"Tom Lane" <tgl@sss.pgh.pa.us> writes:

> Adam PAPAI <wooh@wooh.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

pgsql-bugs by date:

Previous
From: Tom Lane
Date:
Subject: Re: BUG #3665: INSERT is not allowed in a non-volatile function
Next
From: "Jon Roberts"
Date:
Subject: BUG #3667: Job scheduling with Greenplum fails