Databases

NAVIGATION
CATEGORIES
REFERRENCE
LINKS
  • Application errors from upgrading sqlite2-8.13 to sqlite-3.3.5

    1 answers - 941 bytes - related search similar search Add To My Delicious Add To My Stumble Upon Add To My Google Mark Add To My Facebook Add To My Digg Add To My Reddit

    I am using tcl8.4.6 and have upgraded my sqlite from sqlite-2.8-13 to
    sqlite-3.3.5. I originally tried to update my tcl8.4.6 to tcl8.4.11 and
    could not get my application to run. I can get my application to come
    up with tcl8.4.6 and the sqlite-3.3.5 with some problems. After
    changing application calls from sqlite to sqlite3 where needed, the
    application crashes getting a signum 11 error after calling
    sqlite3HashInsert. I have placed fprintf statements in the
    sqlite3HashInsert, so it gets there, it just doesn't return. It appears
    that the arguments are correct in calling the sqlite3HashInsert in
    hash.c. This procedure is called in my application after some parsing
    and detecting a semi-colon.
    Has anyone experienced problems in their application(s) upgrading to
    sqlite-3.3.5 when making a call to sqlite3HashInsert and if so, is there
    a solution to this problem?
    -Bill
  • No.1 | | 1331 bytes | |

    "Sleigher, William H." <William.Sleigher (AT) gd-ais (DOT) comwrote:
    I am using tcl8.4.6 and have upgraded my sqlite from sqlite-2.8-13 to
    sqlite-3.3.5. I originally tried to update my tcl8.4.6 to tcl8.4.11 and
    could not get my application to run. I can get my application to come
    up with tcl8.4.6 and the sqlite-3.3.5 with some problems. After
    changing application calls from sqlite to sqlite3 where needed, the
    application crashes getting a signum 11 error after calling
    sqlite3HashInsert. I have placed fprintf statements in the
    sqlite3HashInsert, so it gets there, it just doesn't return. It appears
    that the arguments are correct in calling the sqlite3HashInsert in
    hash.c. This procedure is called in my application after some parsing
    and detecting a semi-colon.

    Has anyone experienced problems in their application(s) upgrading to
    sqlite-3.3.5 when making a call to sqlite3HashInsert and if so, is there
    a solution to this problem?

    I do not recall any such problem having been seen before.
    Did you compile SQLite and the TCL bindings yourself, or are
    you using a download from the website? What other details
    can you provide? Can you show us the schema of the database
    and the specific SQL statement that is being executed at
    the time of the crash?

Re: Application errors from upgrading sqlite2-8.13 to sqlite-3.3.5


max 4000 letters.
Your nickname that display:
In order to stop the spam: 8 + 7 =
QUESTION ON "Databases"

EMSDN.COM