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. Of course, if some inconsistent
set of preprocessor settings was used, that will become evident without
the optimizations being known. (I highly doubt a SQLite code error in
this case.)
--
Larry Brasfield
_______________________________________________
sqlite-users mailing list
sqlite-users@sqlite.org
http://sqlite.org:8080/cgi-bin/mailman/listinfo/sqlite-users
