Re: [libdbi-users] Valgrind error with pgsql: Conditional jump or move depends on uninitialised value(s)
On 4 Nov 2014, at 12:09, Markus Hoenicka wrote: > At 2014-11-04 11:41 Alex Bligh was heard to say: >> On 3 Nov 2014, at 22:54, Markus Hoenicka >> wrote: >>> I wouldn't bet from valgrind's output that it is libdbi variables which are >>> uninitialized. Can you re-run your test with a different database engine? >>> I'd suggest using the sqlite3 driver as this engine has few if any external >>> dependencies. >> I reran with mysql and it doesn't appear. I presume it's the pgsql dbi >> driver. > > This is one explanation. Another explanation is that the PostgreSQL client > library or one of the libraries it depends on causes these messages. Could > you please fire up the psql command line utility under valgrind and do what > your test program does, i.e. establish a connection? If this test does not > report unitialized variables, we'll have to revisit the pgsql driver. The valgrind nastiness appears even without the correct auth credentials. Running using psql is very odd: $ valgrind psql --username x -W 127.0.0.1 ==14382== Memcheck, a memory error detector ==14382== Copyright (C) 2002-2013, and GNU GPL'd, by Julian Seward et al. ==14382== Using Valgrind-3.10.0.SVN and LibVEX; rerun with -h for copyright info ==14382== Command: /usr/bin/psql --username x -W 127.0.0.1 ==14382== Password for user x: psql: FATAL: Peer authentication failed for user "x" No valgrind errors, but no valgrind summary either. Not quite sure what causes that. -- Alex Bligh -- ___ libdbi-users mailing list libdbi-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/libdbi-users
Re: [libdbi-users] Valgrind error with pgsql: Conditional jump or move depends on uninitialised value(s)
At 2014-11-04 11:41 Alex Bligh was heard to say: > On 3 Nov 2014, at 22:54, Markus Hoenicka > wrote: > >> I wouldn't bet from valgrind's output that it is libdbi variables >> which are uninitialized. Can you re-run your test with a different >> database engine? I'd suggest using the sqlite3 driver as this engine >> has few if any external dependencies. > > I reran with mysql and it doesn't appear. I presume it's the pgsql dbi > driver. This is one explanation. Another explanation is that the PostgreSQL client library or one of the libraries it depends on causes these messages. Could you please fire up the psql command line utility under valgrind and do what your test program does, i.e. establish a connection? If this test does not report unitialized variables, we'll have to revisit the pgsql driver. regards, Markus -- Markus Hoenicka http://www.mhoenicka.de AQ score 38 -- ___ libdbi-users mailing list libdbi-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/libdbi-users
Re: [libdbi-users] Valgrind error with pgsql: Conditional jump or move depends on uninitialised value(s)
On 3 Nov 2014, at 22:54, Markus Hoenicka wrote: > I wouldn't bet from valgrind's output that it is libdbi variables which are > uninitialized. Can you re-run your test with a different database engine? I'd > suggest using the sqlite3 driver as this engine has few if any external > dependencies. I reran with mysql and it doesn't appear. I presume it's the pgsql dbi driver. -- Alex Bligh -- ___ libdbi-users mailing list libdbi-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/libdbi-users
Re: [libdbi-users] Valgrind error with pgsql: Conditional jump or move depends on uninitialised value(s)
At 2014-11-02 19:05 Alex Bligh was heard to say: > I have a very simple program (below) only marginally adapted from the > example here: > > http://libdbi.sourceforge.net/docs/programmers-guide/quickstart-code.html > > which works, but when run through valgrind produces an enormous number > of errors. > The program in its entirety is below. It makes a connection to pgsql, > does no > queries, and immediately shuts the connection. > > I'm not so much worried about the alleged memory leaks but the 85 > instances of > "Conditional jump or move depends on uninitialised value(s)". I don't > know if this is a real problem, but even if not the challenge here > is that /any/ query via dbi is now tainted as uninitialised, so it's > impossible > to see 'real' errors. > > I've not attached a full valgrind dump as it's enormous. However, you > can see > the first two below. > > Any ideas? > Hi, I wouldn't bet from valgrind's output that it is libdbi variables which are uninitialized. Can you re-run your test with a different database engine? I'd suggest using the sqlite3 driver as this engine has few if any external dependencies. regards, Markus -- Markus Hoenicka http://www.mhoenicka.de AQ score 38 -- ___ libdbi-users mailing list libdbi-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/libdbi-users
