Re: BUG #1440: ecpg seg faults - Mailing list pgsql-bugs

From Tom Lane
Subject Re: BUG #1440: ecpg seg faults
Date
Msg-id 24344.1106597017@sss.pgh.pa.us
Whole thread Raw
In response to Re: BUG #1440: ecpg seg faults  (Edmund Bacon <ebacon@onesystem.com>)
Responses Re: BUG #1440: ecpg seg faults  (Edmund Bacon <ebacon@onesystem.com>)
List pgsql-bugs
Edmund Bacon <ebacon@onesystem.com> writes:
> According to the backtrace, it appears to be dieing in malloc.

That's consistent with the idea that the multiple free is the source of
trouble --- multiple free() could corrupt malloc's private data
structures to the point of causing a crash in a later malloc call.

The least painful way of locating the problem would be to relink ecpg
with a debugging malloc package, which could tell you exactly where the
bad free() call is.  You'd probably want to rebuild with --enable-debug
too.

            regards, tom lane

pgsql-bugs by date:

Previous
From: Tom Lane
Date:
Subject: Re: BUG #1433: domain check constraint not checked when adding new column
Next
From: Edmund Bacon
Date:
Subject: Re: BUG #1440: ecpg seg faults