On 3 Mar 2012, at 12:46am, Larry Brasfield <larry_brasfi...@iinet.com> wrote:
>> On 3 Mar 2012, at 12:29am, Larry Brasfield <larry_brasfield at iinet.com> >> wrote: >> >> > That's approaching a pretty good "bug" report. However, I would suggest a >> > little more to promote a resolution of this problem. You do not state the >> > compilation options. Optimization settings and preprocessor variable >> > settings are critical for narrowing what is happening. Also, the >> > preprocessor settings may be the whole problem, one which can be quickly >> > diagnosed for you if they are revealed. >> >> Would the output of 'PRAGMA compile_options;' be sufficient ? > > That's a cute and useful feature I had forgotten. It would be sufficient to > show the preprocessor variable values that were in effect as the amalgamation > was compiled. However, for something that looks like either a SQLite code > error or a gcc code generation error, the optimization settings are also > likely to be needed, and those are not susceptible to that PRAGMA's behavior. Don't forget this isn't is own weird project which may be using the API in an unusual way. It's the shell tool. Possibly even a the version downloaded from the SQLite web site. Given how clear the bug is, with the addition of the bug-reporter's 'PRAGMA compile_options;', I think that's enough information to let the team try to reproduce the behaviour and see what happens. By the way, this shell tool included with a recent version of OS X does not have the problem. 162:~ simon$ which sqlite3 /usr/bin/sqlite3 SQLite version 3.7.7 2011-10-10 22:11:44 sqlite> PRAGMA compile_options; ENABLE_FTS3 ENABLE_FTS3_PARENTHESIS ENABLE_LOCKING_STYLE=1 ENABLE_RTREE OMIT_AUTORESET OMIT_BUILTIN_TEST OMIT_LOAD_EXTENSION TEMP_STORE=1 THREADSAFE=2 Simon. _______________________________________________ sqlite-users mailing list sqlite-users@sqlite.org http://sqlite.org:8080/cgi-bin/mailman/listinfo/sqlite-users
