On Fri, Mar 16, 2012 at 8:41 AM, AlexHr <al...@free.fr> wrote: > > Hello, > > I've just upgraded SQLite from version 3.6.22 to version 3.7.10 and now, > all > my programs crash at run-time. >
This is due to a bug in VS2005. You can work around it yourself by defining _WIN32_WINNT to 0x0400. We have a work-around<http://www.sqlite.org/src/info/1ce4d21d52>in the SQLite sources that will be in the next release. > > It's because, as mentioned before on this mailing-list by darkelf, there is > an inconsistency between #define compilte-time and isNT() run-time. > > All my projects are compiled and used on Windows XP or above. But all my > projects use ANSI character set, not the Unicode one. > > So, I compiled SQLite with SQLITE_WIN32_HAS_ANSI and not > SQLITE_WIN32_HAS_WIDE. > Unfortunately at run-time, all the SQLite code call isNT() (which returns > true) and then call the Unicode functions that make the program crashes. > > The easiest workaround I've found is to write something like: > #if SQLITE_OS_WINCE > # define isNT() (1) > #elif defined SQLITE_WIN32_HAS_ANSI > # define isNT() (0) > > However, that will prevent SQLite to use the LockFileEx() function. > > -- > Alex > > -- > View this message in context: > http://old.nabble.com/-bug--inconsistency-between--define-compilte-time-and-isNT%28%29-run-time-tp33516776p33516776.html > Sent from the SQLite mailing list archive at Nabble.com. > > _______________________________________________ > sqlite-users mailing list > sqlite-users@sqlite.org > http://sqlite.org:8080/cgi-bin/mailman/listinfo/sqlite-users > -- D. Richard Hipp d...@sqlite.org _______________________________________________ sqlite-users mailing list sqlite-users@sqlite.org http://sqlite.org:8080/cgi-bin/mailman/listinfo/sqlite-users
