I get the following segv and stack trace in gdb every time I try
sqlite> EXPLAIN QUERY PLAN ...
where ... is any query you like.
Program received signal SIGSEGV, Segmentation fault.
0x00c33013 in strlen () from /lib/libc.so.6
(gdb) where
#0 0x00c33013 in strlen () from /lib/libc.so.6
#1 0x00e2
Shawn Walker <[EMAIL PROTECTED]> wrote:
> Has anybody run Bounds Checker on SQLite 3?
valgrind (http://valgrind.org/) shows that SQLite3 is free
of memory leaks and buffer overruns.
--
D. Richard Hipp <[EMAIL PROTECTED]>
Shawn Walker <[EMAIL PROTECTED]> wrote:
> Do I need to compile SQLite 3 source code with "-DNDEBUG" for the no debug
> version? I see "NDEBUG" in the source, but wasn't sure.
>
No.
--
D. Richard Hipp <[EMAIL PROTECTED]>
Has anybody run Bounds Checker on SQLite 3? I'm getting a lot of memory
leaks, overruns, etc that is being reported by Bounds Checker. But, what is
strange is that the warning message doesn't match up with the source for
some reason. For example:
Memory Leak Leaving Scope: Variable z refere
Do I need to compile SQLite 3 source code with "-DNDEBUG" for the no debug
version? I see "NDEBUG" in the source, but wasn't sure.
Thanks,
Shawn
Hi, I was just wondering when creating a view, if you could declare a column
as primary key on the view or add in an extra column like viewID?
The reason being is that I am working with the finisar ADO.Net wrapper which
is unable to build commands on tables/views that do not contain primary
keys.
Hello
We have the source code of SQlite 3.3.6 working in the following
configuration:
mingw-win32 compiler (GCC v3.4.2). Our test application works fine with
our small (~22k) test database.
However, on our embedded platform (ARM 9) with the following
configuration
Code-sourcey arm-none-eabi
RohitPatel
wrote:
Will BEGIN IMMEDIATE surely avoid deadlock ? or BEGIN EXCLUSIVE is
better ? i.e. in such cases, what advantage BEGIN IMMEDIATE gives
over BEGIN EXCLUSIVE ?
BEGIN IMMEDIATE will avoid deadlocks when used consistently for all
transactions that begin with SELECT then procee
>>
>> You can avoid the deadlock by having the mixed reader/writer start its
>> transaction with BEGIN IMMEDIATE.
>>
>> Igor Tandetnik
Will BEGIN IMMEDIATE surely avoid deadlock ? or BEGIN EXCLUSIVE is better ?
i.e. in such cases, what advantage BEGIN IMMEDIATE gives over BEGIN
EXCLUSIVE ?
T
Many thanks for helping.
While using SQLite dll Version 3.3.4 on Windows
- Multiple threads/processes access SQLite database,
- Each thread does some SELECTs, INSERTs or UPDATEs.
If for some single SELECT (where user input is used in SQL statement, so to
avoid SQL injection),
sqlite3_prepare(
I use a wrapper that accepts a string of one or more SQL statements. I
scan
through the string looking for "INSERT", "UPDATE" or "DELETE". If I see
any
of those values, I start the whole thing with a "BEGIN IMMEDIATE;". If
none
are found I assume it is a SELECT (read only) and start with a "BEG
VIADANA, Italy (August 11, 2006) - SQLabs today announced the
availability of SQLiteManager 2.1.4, their new SQLite database
manager tool for MacOS X and Windows.
SQLiteManager is a "next generation" GUI database manager for sqlite
databases, it combines an incredible easy to use interface
12 matches
Mail list logo