Ok. My bad for singling out SQLite, I should have rather mentioned that the
problem exists with all memory allocation routines (malloc/free or
new/delete), at least on windows.
A workaround is to pass around allocator / deallocator function pointers
with any data structure which contains pointers
On 2/8/17, Barry Smith wrote:
>
> I believe SQLite doesn't use the standard memory allocation routines, but
> instead has its own routines.
SQLite has its on memory allocation routines (if you use the right
compile-time and start-time options) but it uses system
malloc()/realloc()/free() by defau
Hi Brett,
I believe SQLite doesn't use the standard memory allocation routines, but
instead has its own routines. These (might) use global variables. If each
module of your application statically links to the SQLite source rather than
having SQLite in a common DLL, then each module will have it
Brett Goodman wrote:
> When I call sqlite3_backup_init it throws this error: _/"library /__/
> /__/routine called out of sequence"/_.
To you get an error code, or an exception?
In the first case, try calling sqlite3_errmsg().
The documentation says:
| A call to sqlite3_backup_init() will fail, re
4 matches
Mail list logo
