Bug#638974: libsqlite3-dev: A call to sqlite3_open() gives a SIGSEGV

2015-07-14 Thread Yuriy M. Kaminskiy
On 14.07.2015 11:23, László Böszörményi (GCS) wrote: Hi, On Tue, Jul 14, 2015 at 2:58 AM, Yuriy M. Kaminskiy wrote: Package: libsqlite3-dev Version: 3.8.7.1-1+deb8u1 Followup-For: Bug #638974 1) I was able to reproduce this bug in jessie's 3.8.7.1 (gdb and valgrind report attached); Your i

Bug#638974: libsqlite3-dev: A call to sqlite3_open() gives a SIGSEGV

2015-07-14 Thread GCS
Hi, On Tue, Jul 14, 2015 at 2:58 AM, Yuriy M. Kaminskiy 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

Bug#638974: libsqlite3-dev: A call to sqlite3_open() gives a SIGSEGV

2015-07-13 Thread Yuriy M. Kaminskiy
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); 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 pr

Bug#638974: libsqlite3-dev: A call to sqlite3_open() gives a SIGSEGV

2011-08-23 Thread Mark Caglienzi
Package: libsqlite3-dev Version: 3.7.7-2 Severity: important I'm using this library to develop an application. But as soon as I make a call to sqlite3_open() to open a database, I receive a SIGSEGV. Please note that I followed the basic tutorial (written in the docs and the upstream website) abou