Skip site navigation (1) Skip section navigation (2)

Re: BUG #1440: ecpg seg faults

From: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
To: Edmund Bacon <ebacon(at)onesystem(dot)com>
Cc: Michael Fuhr <mike(at)fuhr(dot)org>, pgsql-bugs(at)postgresql(dot)org
Subject: Re: BUG #1440: ecpg seg faults
Date: 2005-01-24 20:03:37
Message-ID: (view raw, whole thread or download thread mbox)
Lists: pgsql-bugs
Edmund Bacon <ebacon(at)onesystem(dot)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

			regards, tom lane

In response to


pgsql-bugs by date

Next:From: Edmund BaconDate: 2005-01-24 20:17:11
Subject: Re: BUG #1440: ecpg seg faults
Previous:From: Edmund BaconDate: 2005-01-24 19:24:57
Subject: Re: BUG #1440: ecpg seg faults

Privacy Policy | About PostgreSQL
Copyright © 1996-2017 The PostgreSQL Global Development Group