[sqlite] SIGSEGV in sqlite3_open

p Gesendet: Mittwoch, 28. Oktober 2015 12:42 An: General Discussion of SQLite Database Cc: Remuss, Volker (CQTN) Betreff: Re: [sqlite] SIGSEGV in sqlite3_open On 10/28/15, Lohmann, Niels, Dr. (CQTN) wrote: > Hi there, > > unfortunately, the stack trace is truncated: > > (gdb) bt > #0 0x

[sqlite] SIGSEGV in sqlite3_open

-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 On 10/28/2015 01:48 AM, Lohmann, Niels, Dr. (CQTN) wrote: > #0 0x010385c4 in SignalProcmask_r () from > C:\QNX650\target\qnx6/armle-v7/lib/libc.so.3 Have you tried turning off all compiler optimisations? Some older/embedded system compilers can prod

[sqlite] SIGSEGV in sqlite3_open

On 10/28/15, Lohmann, Niels, Dr. (CQTN) wrote: > Hi there, > > unfortunately, I cannot create a better stack trace on short notice. > > However, you may be able to reproduce the problem as follows: > > - Create an in-memory database. > - Release it. > - Create an in-memory database. > - Release it

[sqlite] SIGSEGV in sqlite3_open

Discussion of SQLite Database Cc: Remuss, Volker (CQTN) Betreff: Re: [sqlite] SIGSEGV in sqlite3_open On 10/27/15, Lohmann, Niels, Dr. (CQTN) wrote: > Hi there, > > I experienced a SIGSEGV running the following code: Can you provide us with a stack trace at the point of the crash? >

[sqlite] SIGSEGV in sqlite3_open

On 10/28/15, Lohmann, Niels, Dr. (CQTN) wrote: > Hi there, > > unfortunately, the stack trace is truncated: > > (gdb) bt > #0 0x010385c4 in SignalProcmask_r () from > C:\QNX650\target\qnx6/armle-v7/lib/libc.so.3 > #1 0x010206d8 in pthread_sigmask () from > C:\QNX650\target\qnx6/armle-v7/lib/libc

[sqlite] SIGSEGV in sqlite3_open

Hi there, I experienced a SIGSEGV running the following code: sqlite3* memory_db = NULL; sqlite3_open("file::memory:?cache=shared", &memory_db); To be exact, it occurs when executed a second time. The whole function looks like this void init() { sqlite3* memory_db = NULL;

[sqlite] SIGSEGV in sqlite3_open

On 10/27/15, Lohmann, Niels, Dr. (CQTN) wrote: > Hi there, > > I experienced a SIGSEGV running the following code: Can you provide us with a stack trace at the point of the crash? > > sqlite3* memory_db = NULL; > sqlite3_open("file::memory:?cache=shared", &memory_db); > > To be exact, it

[sqlite] SIGSEGV rolling back in-memory DB‏‎

-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 On 07/08/2015 10:33 AM, Brian Soby wrote: > Nothing appears to happen but it's not running very faithfully. > Specifically, I get a bunch of problems on the rollbacks about the > savepoints not existing even though it's replaying the original > SAVEPOI

[sqlite] SIGSEGV rolling back in-memory DB‏‎

knowing what's going on than anything else. > Date: Wed, 8 Jul 2015 10:19:17 -0700 > From: rogerb at rogerbinns.com > To: sqlite-users at mailinglists.sqlite.org > Subject: Re: [sqlite] SIGSEGV rolling back in-memory DB?? > > -BEGIN PGP SIGNED MESSAGE- > Hash

[sqlite] SIGSEGV rolling back in-memory DB‏‎

-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 On 07/08/2015 09:55 AM, Brian Soby wrote: > It's single threaded. Good - that eliminates a whole bunch of complications. > I have a log of all of the queries run through the database up > until the crash. It crashes on a rollback command. What happe

[sqlite] SIGSEGV rolling back in-memory DB‏‎

al. I can send the log off-list to anyone who wants it. I could also send a dockerfile to recreate the problem. Any interest? > Date: Tue, 7 Jul 2015 15:41:32 -0700 > From: rogerb at rogerbinns.com > To: sqlite-users at mailinglists.sqlite.org > Subject: Re: [sqlite] SIGSEGV rolling

[sqlite] SIGSEGV rolling back in-memory DB‏‎

On 7 Jul 2015, at 10:06pm, Brian Soby wrote: > I don't have an easy way to recreate the problem since it takes quite a bit > of app code to run the test suite that triggers the problem. I can however > provide any output of anything you'd like. Can you log the commands that your test suite e

[sqlite] SIGSEGV rolling back in-memory DB‏‎

On 7 Jul 2015, at 6:49pm, Roger Binns wrote: > No need to badger, I am happy to help :-) Simon.

[sqlite] SIGSEGV rolling back in-memory DB‏‎

-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 On 07/07/2015 02:06 PM, Brian Soby wrote: > I don't believe it's a python specific issue since the core problem > occurs in a rollback command internal to SQLlite. Unless you configure it otherwise, pysqlite likes to parse your SQL and do extra operat

[sqlite] SIGSEGV rolling back in-memory DB‏‎

e any output of anything you'd like. > Date: Tue, 7 Jul 2015 12:47:48 -0400 > From: drh at sqlite.org > To: sqlite-users at mailinglists.sqlite.org > Subject: Re: [sqlite] SIGSEGV rolling back in-memory DB?? > > On 7/7/15, Brian Soby wrote: > > Yes, it appears to a

[sqlite] SIGSEGV rolling back in-memory DB‏‎

On 7/7/15, Brian Soby wrote: > Yes, it appears to also happen on 3.8.10-2. I tested by building pysqlite > and replacing python's sqlite3 module with that, statically linked against > the current amalgamation release from sqlite.org. I used the stack trace for > 14.04's sqlite v3.8.2 since I could

[sqlite] SIGSEGV rolling back in-memory DB‏‎

-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 On 07/07/2015 09:47 AM, Richard Hipp wrote: > Can you send instructions on how to recreate the problem? Please > bare in mind that none of the core SQLite developers do much with > python. Alternatively, you might send emails to Roger Binns and > badg

[sqlite] SIGSEGV rolling back in-memory DB‏‎

python-dbg for the debug info. > Date: Tue, 7 Jul 2015 08:19:53 -0400 > From: drh at sqlite.org > To: sqlite-users at mailinglists.sqlite.org > Subject: Re: [sqlite] SIGSEGV rolling back in-memory DB?? > > On 7/6/15, Brian Soby wrote: > > Related to this bug: https://c

[sqlite] SIGSEGV rolling back in-memory DB‏‎

On 7/6/15, Brian Soby wrote: > Related to this bug: https://code.djangoproject.com/ticket/24080 > > I can reliably duplicate on Ubuntu 14.04 (package details at bottom) but I > can't seem to create a stripped codebase to repro the issue. GDB stacktrace > and package details are below. This only ap

[sqlite] SIGSEGV rolling back in-memory DB‏‎

Related to this bug: https://code.djangoproject.com/ticket/24080 I can reliably duplicate on Ubuntu 14.04 (package details at bottom) but I can't seem to create a stripped codebase to repro the issue. GDB stacktrace and package details are below. This only appears to happen for in-memory databases

Re: [sqlite] SIGSEGV Error when using sqlite3_exec( )

On Thu, Feb 10, 2011 at 9:59 PM, Zaryab M. Munir wrote: > [zm]: No there is no other function read() and I did compile glibc. I want > to check if it is static or dynamic. Is static linking a requirement ? > Thanks. > If you're linking to libXXX.so then it's dynamically linked. sqlite3 can be

Re: [sqlite] SIGSEGV Error when using sqlite3_exec( )

--- On Thu, 2/10/11, Pavel Ivanov wrote: > From: Pavel Ivanov > Subject: Re: [sqlite] SIGSEGV Error when using sqlite3_exec( ) > To: "General Discussion of SQLite Database" > Cc: "Zaryab Munir (zmunir)" > Date: Thursday, February 10, 2011, 12:28 PM >

Re: [sqlite] SIGSEGV Error when using sqlite3_exec( )

On Thu, Feb 10, 2011 at 2:22 PM, Zaryab M. Munir wrote: > Thanks,  my reply inline: > Sincerely, > Zaryab > > > --- On Thu, 2/10/11, Pavel Ivanov wrote: > >> From: Pavel Ivanov >> Subject: Re: [sqlite] SIGSEGV Error when using sqlite3_exec( ) >> To: &q

Re: [sqlite] SIGSEGV Error when using sqlite3_exec( )

Thanks, my reply inline: Sincerely, Zaryab --- On Thu, 2/10/11, Pavel Ivanov wrote: > From: Pavel Ivanov > Subject: Re: [sqlite] SIGSEGV Error when using sqlite3_exec( ) > To: "General Discussion of SQLite Database" > Cc: "Zaryab Munir (zmunir)" > Date: T

Re: [sqlite] SIGSEGV Error when using sqlite3_exec( )

Zaryab, There's no need to repeat your email several times. >    Question1:  Can I have multiple connections opened for each thread to >    the same in-memory dbase. No. Each connection to ":memory:" creates unique in-memory database which will be deleted when that connection is closed. >    Qu

[sqlite] SIGSEGV Error when using sqlite3_exec( )

Hi, I am using an in-memory dbase in a multi-threaded application and have the following two questions: I create dbase connections by each thread using the API: { Sqlite3 *db =3D NULL; Sqlite3_open(":memory:", &db); When I try to use sqlite3_exec( ) I get segment

[sqlite] SIGSEGV error when using sqlite3_exec()

I am using an in-memory dbase in a multi-threaded application and have the following two questions: I create dbase connections by each thread using the API: { Sqlite3 *db =3D NULL; Sqlite3_open(":memory:", &db); When I try to use sqlite3_exec( ) I get segmentation

Re: [sqlite] SIGSEGV on INSERT DEFAULT VALUES with triggers

On Tue, Apr 13, 2010 at 12:30 PM, Tomasz Ł. Nowak < tomasz.no...@man.poznan.pl> wrote: > Shane, you wrote: > > I could not reproduce this on the current or 3.6.23 build: > > > > >./sqlite3 -version > > 3.6.23 > > > > >cat script.sql > > CREATE TABLE current(x,y,z); > > INSERT INTO current DEFAULT

Re: [sqlite] SIGSEGV on INSERT DEFAULT VALUES with triggers

Shane, you wrote: > I could not reproduce this on the current or 3.6.23 build: > > >./sqlite3 -version > 3.6.23 > > >cat script.sql > CREATE TABLE current(x,y,z); > INSERT INTO current DEFAULT VALUES ('a', 'b', 30); > > >./sqlite3 -init script.sql > -- Loading resources from script.sql > Error:

Re: [sqlite] SIGSEGV on INSERT DEFAULT VALUES with triggers

Can you provide more details? What options are you using? What version of the source? Amalgamation? Preprocessed? Complete package? I could not reproduce this on the current or 3.6.23 build: >./sqlite3 -version 3.6.23 >cat script.sql CREATE TABLE current(x,y,z); INSERT INTO current DEFAULT VAL

[sqlite] SIGSEGV on INSERT DEFAULT VALUES with triggers

Hi! A bug resulting in a crash (segmentation fault) of sqlite3 has been detected. Please find attached the script causing problems and a debug session log. Tested to be vulnerable: linux 3.6.23 linux 3.6.22 linux 3.6.4 solaris 3.5.1 Tested to be invulnerable: linux 2.8.17 Best wishes Tomasz Now

[sqlite] SIGSEGV

Hi everyone. Im developing my program in C++ and using i386 linux as OS. Im having some problem with SQLite 2.8.6. In my program I have a method wich is a void and its call a Callback function to do a query of DB in SQLite. I whant to do another sqlite_exec() inside a callback funcion of a previ