During valgrind ( www.valgrind.org ) testing under linux I was executing "vaccum" and got:
==17449== Conditional jump or move depends on uninitialised value(s) ==17449== at 0x1CF2200C: sqlite3GenerateConstraintChecks (insert.c:980) ==17449== by 0x1CF233F6: sqlite3Insert (insert.c:629) ==17449== by 0x1CF2B72E: sqlite3Parser (parse.y:600) ==17449== by 0x1CF377BD: sqlite3RunParser (tokenize.c:388) ==17449== by 0x1CF2ED6B: sqlite3_prepare (prepare.c:440) ==17449== by 0x1CF3B376: execSql (vacuum.c:42) ==17449== by 0x1CF3B429: execExecSql (vacuum.c:61) ==17449== by 0x1CF3B721: sqlite3RunVacuum (vacuum.c:207) ==17449== by 0x1CF3D6AD: sqlite3VdbeExec (vdbe.c:4288) ==17449== by 0x1CF40F7B: sqlite3_step (vdbeapi.c:217) Is this already known, or should I enter a bug? Are pre-release regression tests done under valgrind or purify? Might be a good idea. Thx Russ
