gt;
>
>
>> Fri Sep 04 2015 4:57:57 pm CEST CEST from "Domingo Alvarez Duarte"
>> Subject: Re: [sqlite] SQLite3 trunk error
>> with
>> old database with fts3/4
>>
>> Hello !
>>
>> I did something similar to your sugestion (
en better is not to leak statement handle pointers. The
sqlite3_next_stmt() API should really only be used to help track down
leaks, not to do cleanup.
Dan.
>
>> Fri Sep 04 2015 4:18:01 pm CEST CEST from "Domingo Alvarez Duarte"
>> Subject: Re: [sqlite] SQ
On 09/04/2015 09:18 PM, Domingo Alvarez Duarte wrote:
> Hello !
>
> I'm not sure where the problem is but this code worked without any problem
> with previous sqlite3.
>
> Here is a backtrace of a segfault using gdb (the line numbers will not match
> standard sqlite3.c because I have some custom ex
On 09/04/2015 07:35 PM, Domingo Alvarez Duarte wrote:
> Hello !
>
> After fix the index issues using an old sqlite3 executable (the trunk refuse
> to work on indexes created with single quotes on field names) I'm getting
> ocasionaly memory errors when using fts3/4 searches, see error below:
>
> fr
the db handle to sqlite3_next_stmt() - the data structure
> may have already been freed.
>
> Dan.
>
>
>
>
>
>>Thanks a lot for your help !
>>
>>
>>
>>
>>>Fri Sep 04 2015 4:57:57 pm CEST CEST from "Domingo Alvarez Duarte"
z Duarte"
> Subject: Re: [sqlite] SQLite3 trunk error with
>old database with fts3/4
>
> Hello again !
>
> I looked at the documentaion again and realized that I was alread calling
> sqlite3_close_v2 the I commented out all of the sqlite3_next_stmt cleanup
>and
>
a lot for your help !
> Fri Sep 04 2015 4:57:57 pm CEST CEST from "Domingo Alvarez Duarte"
> Subject: Re: [sqlite] SQLite3 trunk error with
>old database with fts3/4
>
> Hello !
>
> I did something similar to your sugestion (sqlite3_next_stmt(db, NULL))?
&
etect
it and skip it ?
Or any way to safely have a central point to do a cleanup ?
Cheers !
> Fri Sep 04 2015 4:44:02 pm CEST CEST from "Dan Kennedy"
> Subject: Re: [sqlite] SQLite3 trunk error with old
>database with fts3/4
>
> On 09/04/2015 09:29 PM, Domingo Alvarez Du
sql(statement));
??? sqlite3_finalize(statement);
??? count++;
??? }
?
> Fri Sep 04 2015 4:33:13 pm CEST CEST from "Dan Kennedy"
> Subject: Re: [sqlite] SQLite3 trunk error with old
>database with fts3/4
>
> On 09/04/2015 09:18 PM, Domingo Alvarez Duarte wrote:
>
On 4 Sep 2015, at 4:23pm, Domingo Alvarez Duarte
wrote:
> I think that would be interesting to have functions similar to
> sqlite3_next_stmt/sqlite3_finalize for extensions something like this:
>
>
> sqlite3_next_extension / sqlite3_finalize_extension
Almost nobody uses sqlite3_next_stmt
t;Domingo Alvarez Duarte"
> Subject: Re: [sqlite] SQLite3 trunk error with
>old database with fts3/4
>
> Hello !
>
> I'm not sure where the problem is but this code worked without any problem
> with previous sqlite3.
>
> Here is a backtrace of a segfault u
t sqlite3.c:68941
#5? 0x004e6044 in sqlite3VdbeFinalize (p=0x7fffe408ac88)
??? at sqlite3.c:68861
#6? 0x004e60cd in sqlite3_finalize (pStmt=0x7fffe408ac88)
??? at sqlite3.c:70500
?
> Fri Sep 04 2015 4:05:12 pm CEST CEST from "Dan Kennedy"
> Subject: Re: [sqlite] SQLite3 trun
Hello !
After fix the index issues using an old sqlite3 executable (the trunk refuse
to work on indexes created with single quotes on field names) I'm getting
ocasionaly memory errors when using fts3/4 searches, see error below:
free(): corrupted unsorted chunks: 0x7fa3a01073a0
?
Ch
13 matches
Mail list logo
