Following code will freeze app on std.gc.fullCollect(), when sqlite3_close() in
destructor is called. If destructor is called manualy, everything goes ok.
Is it a bug, and if is, with what? It behaves same on winxp64 and centos5.2
using dmd 1.30 and sqlite 3.6.5 or 3.6.19 statically import lib.
Object destructors can be tricky in a GC'd language. It looks like you're
accessing a deallocated pointer in your destructor. Order of
collection/destruction is not guaranteed.
Bane Wrote:
> Following code will freeze app on std.gc.fullCollect(), when sqlite3_close()
> in destructor is called.
Bane wrote:
Following code will freeze app on std.gc.fullCollect(), when sqlite3_close() in
destructor is called. If destructor is called manualy, everything goes ok.
Is it a bug, and if is, with what? It behaves same on winxp64 and centos5.2
using dmd 1.30 and sqlite 3.6.5 or 3.6.19 staticall
grauzone Wrote:
> Bane wrote:
> > Following code will freeze app on std.gc.fullCollect(), when
> > sqlite3_close() in destructor is called. If destructor is called manualy,
> > everything goes ok.
> >
> > Is it a bug, and if is, with what? It behaves same on winxp64 and centos5.2
> > using dmd
