Hi,
On Tue, Jul 14, 2015 at 2:58 AM, Yuriy M. Kaminskiy <yum...@gmail.com> wrote:
> Package: libsqlite3-dev
> Version: 3.8.7.1-1+deb8u1
> Followup-For: Bug #638974
>
> FYI:
> 1) I was able to reproduce this bug in jessie's 3.8.7.1 (gdb and valgrind
> report attached);
Your issue is quite different from the one you sent this followup
for. The gdb report is missing, but it would be useful for upstream,
not me. :(
> 2) I was *NOT* able to reproduce it in (self-backported) sid's 3.8.10.2-1
> (and running under valgrind does not show any problem).
> [fwiw, test.db created sid {totally expectdly} kills jessie's on attempt
> to open it].
> However, I have not found respective entry in changelogs (or upstream
> commit), so this could be false positive.
It can be an old upstream bug. If you have time, you may try to find
the commit which fixes this from the upstream repository. From the
valgrind output it seems you execute: 'sqlite3 test.db "CREATE TABLE t
( x UNIQUE PRIMARY KEY ) WITHOUT ROWID;"'. The root cause can be that
'primary key' is an alias of 'unique'[1] (point 3.0, second
paragraph). At least the solution to drop the "double" 'unique'
statement and just use 'sqlite3 test.db "CREATE TABLE t ( x PRIMARY
KEY ) WITHOUT ROWID;"'.
Regards,
Laszlo/GCS
[1] https://www.sqlite.org/withoutrowid.html
--
To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
