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
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
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
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