Received: from maia.hub.org (maia-3.hub.org [200.46.204.243]) by mail.postgresql.org (Postfix) with ESMTP id 3981F633D83 for ; Fri, 7 May 2010 16:38:54 -0300 (ADT) Received: from mail.postgresql.org ([200.46.204.86]) by maia.hub.org (mx1.hub.org [200.46.204.243]) (amavisd-maia, port 10024) with ESMTP id 01484-05; Fri, 7 May 2010 19:38:46 +0000 (UTC) X-Greylist: from auto-whitelisted by SQLgrey-1.7.6 X-Greylist: from auto-whitelisted by SQLgrey-1.7.6 Received: from dukecmmtar04.coxmail.com (dukecmmtar04.coxmail.com [68.99.120.47]) by mail.postgresql.org (Postfix) with ESMTP id 17820633D67; Fri, 7 May 2010 16:38:46 -0300 (ADT) Received: from dukecmimpo03.coxmail.com ([68.99.120.137]) by dukecmmtar04.coxmail.com (InterMail vM.7.05.02.00 201-2174-114-20060621) with ESMTP id <20100507193846.MXEU29838.dukecmmtar04.coxmail.com@dukecmimpo03.coxmail.com>; Fri, 7 May 2010 15:38:46 -0400 Received: from Lorien.local ([98.172.21.99]) by dukecmimpo03.coxmail.com with bizsmtp id Ejel1e00L28G7zW01jelFt; Fri, 07 May 2010 15:38:46 -0400 Message-ID: <4BE46C45.1050105@pnlassociates.com> Date: Fri, 07 May 2010 15:38:45 -0400 From: Paul Anderson User-Agent: Mozilla/5.0 (Macintosh; U; Intel Mac OS X 10.6; en-US; rv:1.9.1.9) Gecko/20100317 Lightning/1.0b1 Thunderbird/3.0.4 MIME-Version: 1.0 To: Michael Meskes CC: pgsql-testers@postgresql.org Subject: Re: Glibc error using ecpg References: <20100507190040.GB9360@feivel.credativ.lan> In-Reply-To: <20100507190040.GB9360@feivel.credativ.lan> Content-Type: text/plain; charset=UTF-8; format=flowed Content-Transfer-Encoding: 7bit X-Virus-Scanned: Maia Mailguard 1.0.1 X-Spam-Status: No, hits=-1.9 tagged_above=-10 required=5 tests=BAYES_00=-1.9 X-Spam-Level: X-Archive-Number: 201005/16 X-Sequence-Number: 99 It reviewing the output, I'm thinking this is a bug in my test framework, not in ecpg. Do you agree? Paul On 5/7/10 3:00 PM, Michael Meskes wrote: > 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 >