From: Michael Meskes <meskes@postgresql.org>
To: paul.a@pnlassociates.com
Cc: pgsql-testers@postgresql.org
Subject: Re: Glibc error using ecpg
Date: Fri, 7 May 2010 21:00:40 +0200
Message-ID: <20100507190040.GB9360@feivel.credativ.lan> (raw)
Hi Paul,
could you compile ecpg with debugging enabled and then run your test case under
gdb? A run under valgrind might help too. This bug shows some memory
corruption, so I need to figure out where exatly this happens.
Alternatively a small test case with which I can reproduce the problem on my
system is an option too.
Thanks a lot for your effort.
Michael
--
Michael Meskes
Michael at Fam-Meskes dot De, Michael at Meskes dot (De|Com|Net|Org)
Michael at BorussiaFan dot De, Meskes at (Debian|Postgresql) dot Org
ICQ 179140304, AIM/Yahoo/Skype michaelmeskes, Jabber meskes@jabber.org
VfL Borussia! Força Barça! Go SF 49ers! Use Debian GNU/Linux, PostgreSQL
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Reply to all the recipients from your mail client; the link fills in
the headers below: reply via email
Some clients, webmail especially, drop In-Reply-To and References from
a link, and the reply then starts a new thread: use the mbox below.
To: pgsql-testers@postgresql.org
Cc: meskes@postgresql.org, paul.a@pnlassociates.com
Subject: Re: Glibc error using ecpg
In-Reply-To: <20100507190040.GB9360@feivel.credativ.lan>
References: <20100507190040.GB9360@feivel.credativ.lan>
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
This inbox is served by DDX for PostgreSQL; see mirroring instructions
for how to clone and mirror all data and code used for this inbox