Get rid of the comma at the end of the 'timestamp' line.
Rick
On Aug 8, 2012, at 10:03 PM, Brandon Pimenta wrote:
> I just found a bug in SQLite. It says "1: near ")": syntax error". Here's
> my SQL query:
>
> CREATE TABLE online_status (
> username varchar(255) NOT NULL default '',
>
INSERT INTO myTable (Rd, en, ue) SELECT 'aa', 'bb', ue FROM othertable;
Rick
On Jul 22, 2012, at 7:41 PM, YAN HONG YE wrote:
> INSERT INTO myTable (Rd, en, ue) VALUES ("aa","bb",select ue from othertable);
___
sqlite-users mailing list
Thanks. I'll hold off on checking the result of every sqlite3_bind_* for now.
It's unlikely I'm using a finalized statement otherwise I believe I would get a
given crash much more often. The sqlite3_prepare_v2 statements that are failing
only fail occasionally, not every time. But I'll double
:00 PM, Richard Hipp wrote:
> On Thu, Jul 19, 2012 at 1:56 PM, Rick Maddy <rma...@gmail.com> wrote:
>
>> What about checking all the sqlite3_bind_* methods? Is it possible any of
>> those could cause the problems I'm seeing?
>>
>
> Being busing with oth
What about checking all the sqlite3_bind_* methods? Is it possible any of those
could cause the problems I'm seeing?
Rick
On Jul 19, 2012, at 11:42 AM, Simon Slavin wrote:
>
> On 19 Jul 2012, at 6:03pm, Rick Maddy <rma...@gmail.com> wrote:
>
>> Thanks. Time to add
not all, and none of the 'prepare' statements.
Thanks,
Rick
On Jul 19, 2012, at 11:42 AM, Simon Slavin wrote:
>
> On 19 Jul 2012, at 6:03pm, Rick Maddy <rma...@gmail.com> wrote:
>
>> Thanks. Time to add checks to nearly 400 prepare and step statements.
>
> Sorry
But that would flag valid state changes just as much as it would flag corrupted
memory.
Rick
On Jul 19, 2012, at 11:15 AM, Black, Michael (IS) wrote:
> It could easiliy be expanded to look at the whole structure...
>
>
>
> Or just do an XOR checksum on the bytes in sizeof(sqlite3) and
Thanks but doesn't that code check to see if the database pointer has changed
and not whether the memory it references has been corrupted? I guess that's a
start though.
Rick
On Jul 19, 2012, at 11:02 AM, Black, Michael (IS) wrote:
> Buffer overflow issues can cause problems at seemingly
Thanks. Time to add checks to nearly 400 prepare and step statements.
Rick
___
sqlite-users mailing list
sqlite-users@sqlite.org
http://sqlite.org:8080/cgi-bin/mailman/listinfo/sqlite-users
ng to help if the prepare statement crashes before returning?
Thanks,
Rick
On Jul 19, 2012, at 10:32 AM, Simon Slavin wrote:
>
> On 19 Jul 2012, at 5:09pm, Rick Maddy <rma...@gmail.com> wrote:
>
>> Exception Type: SIGSEGV
>> Exception Codes: SEGV_ACCERR at 0x1a
>
For quite some time now I've been getting reports of crashes in my iOS app.
Specifically these are caused by crashes in sqlite3_prepare_v2 and sqlite_step.
The associated code works fine most of the time. So I'm looking for thoughts on
how to find and fix the problem since there seems to be no
11 matches
Mail list logo
