Re: [libdbi-users] Valgrind error with pgsql: Conditional jump or move depends on uninitialised value(s)

2014-11-04 Thread Alex Bligh
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 > dependencie

Re: [libdbi-users] Valgrind error with pgsql: Conditional jump or move depends on uninitialised value(s)

2014-11-04 Thread Markus Hoenicka
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 dr

Re: [libdbi-users] Valgrind error with pgsql: Conditional jump or move depends on uninitialised value(s)

2014-11-04 Thread Alex Bligh
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