Re: Huge amount of memory errors with libpq

From: Casey Jones <jonescaseyb(at)gmail(dot)com>
To: pgsql-general(at)postgresql(dot)org
Subject: Re: Huge amount of memory errors with libpq
Date: 2010-09-13 01:23:32
Message-ID: 201009122023.32781.jonescaseyb@gmail.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-general

On Sunday 12 September 2010 5:44:26 pm you wrote:
> Casey Jones <jonescaseyb(at)gmail(dot)com> writes:
> > I don't think valgrind is the only issue here because outside valgrind my
> > data is getting magically overwritten. In the function causing that
> > problem I set all the fields I wanted to set by hand instead of using
> > PQgetvalue().
> >
> > If I leave PQexec() uncommented, my data in a totally unrelated area
> > would
> >
> > change, but when I comment it out I get the expected results. There
> > might be an error I'm making thats causing this, but I can't find it in
> > valgrind because of the huge number of errors.
>
> FWIW, that test case shows no errors at all for me, on an x86_64 running
> Fedora 13. I'd suggest trying it on something other than Gentoo.
>
> regards, tom lane

I set up Fedora 13 and ran the test case, and I didn't get any errors. I also
tested my project and it had significantly fewer errors. So yeah, it looks
like a glibc problem on Gentoo. Thanks for the help everyone.

--
Casey Jones

In response to

Browse pgsql-general by date

  From Date Subject
Next Message Craig Ringer 2010-09-13 01:58:52 Re: Monitoring Object access
Previous Message Yaroslav Tykhiy 2010-09-13 00:59:48 Schema search path