On Sep 30, 2009, at 1:09 AM, Ralf Junker wrote:
> At 14:04 29.09.2009, Dan Kennedy wrote:
>
>> On Sep 29, 2009, at 4:30 PM, Ralf Junker wrote:
>>
>>> My memory manager reports that the SQL below results in memory being
>>> reused after it has already been freed when it is RUN FOR A SECOND
>>>
At 14:04 29.09.2009, Dan Kennedy wrote:
>On Sep 29, 2009, at 4:30 PM, Ralf Junker wrote:
>
>> My memory manager reports that the SQL below results in memory being
>> reused after it has already been freed when it is RUN FOR A SECOND
>> TIME on the same database connection.
>
>Hi Ralf,
>
At 14:04 29.09.2009, Dan Kennedy wrote:
>On Sep 29, 2009, at 4:30 PM, Ralf Junker wrote:
>
>> My memory manager reports that the SQL below results in memory being
>> reused after it has already been freed when it is RUN FOR A SECOND
>> TIME on the same database connection.
>
>Hi Ralf,
>
On Sep 29, 2009, at 4:30 PM, Ralf Junker wrote:
> My memory manager reports that the SQL below results in memory being
> reused after it has already been freed when it is RUN FOR A SECOND
> TIME on the same database connection.
Hi Ralf,
Thanks for this report. I'm unable to reproduce the
My memory manager reports that the SQL below results in memory being reused
after it has already been freed when it is RUN FOR A SECOND TIME on the same
database connection.
Psydocode (I do not run C):
sqlite3_initialize;
sqlite3_open(DB_FILE_NAME, );
sqlite3_exec(DB, SQL, NULL, NULL,
5 matches
Mail list logo