[sqlite] SIGSEGV in sqlite3_open

2015-10-28 Thread Lohmann, Niels, Dr. (CQTN)
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

2015-10-28 Thread Roger Binns
-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

2015-10-28 Thread Richard Hipp
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

2015-10-28 Thread Lohmann, Niels, Dr. (CQTN)
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

2015-10-28 Thread Richard Hipp
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

2015-10-27 Thread Lohmann, Niels, Dr. (CQTN)
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

2015-10-27 Thread Richard Hipp
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