Well, I'm pretty sure I haven't. FYI, I wrapped the sqlite3_stmt into a class and only call its sqlite3_finalize on its destructor. So there's no way that it would be called twice. Or so I think.
Pavel Ivanov wrote: >> The pPrior or p pointer isn't null so it should've been >> freed without error IMHO. Can anybody tell me what's wrong with it? >> Thanks >> a lot in advance. > > If "pPrior or p pointer" isn't null but was already freed then double > free can cause segmentation fault. In other words most probably you're > calling sqlite3_finalize on already finalized statement. > > Pavel > > On Tue, Oct 13, 2009 at 5:58 AM, <ben...@cs.its.ac.id> wrote: >> Hi there, I'm a new member of the mailing list. Nice to meet you all. >> >> BTW, I've got one problem that's been bugging me for weeks. >> >> Occasionally (not always), I got a seg fault at "static void >> sqlite3MemFree(void *pPrior)". It happened when I do sqlite3_reset or >> sqlite3_finalize. The pPrior or p pointer isn't null so it should've >> been >> freed without error IMHO. Can anybody tell me what's wrong with it? >> Thanks >> a lot in advance. >> >> >> Fare thee well, >> Bawenang R. P. P. >> >> ---------------- >> "If a picture is worth a thousand words, an animations is worth a >> thousand >> pictures. And to take that a step further, a game is worth a thousand >> animations." Peter Raad, Executive Director, The Guildhall at SMU >> >> >> -- Fare thee well, Bawenang R. P. P. ---------------- "If a picture is worth a thousand words, an animations is worth a thousand pictures. And to take that a step further, a game is worth a thousand animations." Peter Raad, Executive Director, The Guildhall at SMU -- http://www.its.ac.id _______________________________________________ sqlite-users mailing list sqlite-users@sqlite.org http://sqlite.org:8080/cgi-bin/mailman/listinfo/sqlite-users
