From: Guy Deleeuw <G.De_Leeuw@eurofer.be>
To: pgsql-admin@postgresql.org <pgsql-admin@postgresql.org>
Subject: valgrind error
Date: Wed, 16 Jun 2010 10:27:48 +0200
Message-ID: <4C188B04.8030507@eurofer.be> (raw)
Hello
When using valgrind with one of my program a have these error from
PQconnectdb.
Debian lenny last update.
postgresql 8.3
Regards
Guy
guy@vsStats:src# valgrind /usr/local/lassie/bin/gdExecJob -i
/var/www/users/guy/gdQuery2/testTextEdit -o /tmp/textedit.rpg
==20166== Memcheck, a memory error detector.
==20166== Copyright (C) 2002-2007, and GNU GPL'd, by Julian Seward et al.
==20166== Using LibVEX rev 1854, a library for dynamic binary translation.
==20166== Copyright (C) 2004-2007, and GNU GPL'd, by OpenWorks LLP.
==20166== Using valgrind-3.3.1-Debian, a dynamic binary instrumentation
framework.
==20166== Copyright (C) 2000-2007, and GNU GPL'd, by Julian Seward et al.
==20166== For more details, rerun with: -v
==20166==
Starting /var/www/users/guy/gdQuery2/testTextEdit processing to file
/tmp/textedit.rpg
Matched extension : .rpg
==20166== Conditional jump or move depends on uninitialised value(s)
==20166== at 0x9C5C1EF: BN_mod_inverse (in /usr/lib/libcrypto.so.0.9.8)
==20166== by 0x9C5F8D1: BN_MONT_CTX_set (in /usr/lib/libcrypto.so.0.9.8)
==20166== by 0x9C5FB5F: BN_MONT_CTX_set_locked (in
/usr/lib/libcrypto.so.0.9.8)
==20166== by 0x9C723DF: (within /usr/lib/libcrypto.so.0.9.8)
==20166== by 0x9C73E18: RSA_verify (in /usr/lib/libcrypto.so.0.9.8)
==20166== by 0x9983974: ssl3_get_key_exchange (in
/usr/lib/libssl.so.0.9.8)
==20166== by 0x9985377: ssl3_connect (in /usr/lib/libssl.so.0.9.8)
==20166== by 0x6158932: (within /usr/lib/libpq.so.5.1)
==20166== by 0x614A246: PQconnectPoll (in /usr/lib/libpq.so.5.1)
==20166== by 0x614B1FD: (within /usr/lib/libpq.so.5.1)
==20166== by 0x614D01E: PQconnectdb (in /usr/lib/libpq.so.5.1)
==20166== by 0x661CE96: gdCoreSql::connectDB() (in
/usr/local/lassie/lib/libgdcore.so.1.0.1)
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 using the --to and --cc options:
reply via email
To: pgsql-admin@postgresql.org
Cc: G.De_Leeuw@eurofer.be
Subject: Re: valgrind error
In-Reply-To: <4C188B04.8030507@eurofer.be>
* 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