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. Information below is just FYI. >Are you compiling SQLite with any special symbols or anything >like that? Not that I am aware of. Certainly nothing except the usual which I did before the problem surfaced. >Are you able to build other programs using this memory manager? If so, >does the bug show up when you pass the problematic SQL to the command >line tool twice? Or if I send you a C program are you able to build and >test it? I am not able to use the exact same memory manager when I run C code directly. Alternatively, I did just now run SQLite on Embarcadero's C++ Builder with CodeGuard enabled. This results in a magnitude of error reports while the SQLite code still produces correct results AFAIKS. It is impossible for me to tell if these reports also contain the one I reported earlier. Knowing little about how well CodeGuard does its job, I am not sure how seriously I shall take its warnings as long as all works well. Ralf _______________________________________________ sqlite-users mailing list sqlite-users@sqlite.org http://sqlite.org:8080/cgi-bin/mailman/listinfo/sqlite-users
