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 >>> TIME on the same database connection. >> >> Hi Ralf, >> >> Thanks for this report. I'm unable to reproduce the problem so far >> though. > > No longer needed. The problem no longer shows with check-in > [582bd76828] applied. In fact I believed that it was initiated by my > report on this list.
It was. valgrind reported that the code was using an uninitialized variable when running your SQL sample. Now that I look at it a second time I can see how that led to writing to freed memory, as the bounds checker reported. Thanks for following up. Dan. _______________________________________________ sqlite-users mailing list sqlite-users@sqlite.org http://sqlite.org:8080/cgi-bin/mailman/listinfo/sqlite-users
