> However, bus errors are often the result of something in your own code, or of > not checking the result codes returned by all your previous SQLite3 calls.
Simon, You are confusing bus errors with segmentation faults. They are different things and bus errors inside SQLite can never be caused by the code using SQLite. Pavel On Sun, Sep 9, 2012 at 9:34 AM, Simon Slavin <slav...@bigfraud.org> wrote: > > On 9 Sep 2012, at 12:49pm, Tal Tabakman <tal.tabak...@gmail.com> wrote: > >> "CREATE >> INDEX IDX_OBJ on entries (obj_id, path);;" > > Just on the offchance, please try it with just one semi-colon, and again with > no semi-colons. I don't think that's the problem, but it might show up > something different. > > However, bus errors are often the result of something in your own code, or of > not checking the result codes returned by all your previous SQLite3 calls. > Are you checking the integers returned by all the SQLite3 calls and making > sure they're SQLITE_OK ? > > Simon. > _______________________________________________ > sqlite-users mailing list > sqlite-users@sqlite.org > http://sqlite.org:8080/cgi-bin/mailman/listinfo/sqlite-users _______________________________________________ sqlite-users mailing list sqlite-users@sqlite.org http://sqlite.org:8080/cgi-bin/mailman/listinfo/sqlite-users
