On 12/12/07, CAVALO SCHMIDT <[EMAIL PROTECTED]> wrote: > For example, in a database where searching for text "key1" (column a) > returns "value1", "value2", "value3", and "value4" in column b, the callback > fnuction of that code would be called THREE times, returning thus three > message boxes: > - key1 -> value1 > - key1 -> value2 > - key1 -> value3 > And, in the fourth call to the callback function in this same sqlite3_exec > call, it gives "Access Violation", and never gets to reach the callback > function for the fourth time. But, if there were only value1, value2 and > value3, it would work fine. Actually, if we called, several times, > sqlite3_exec() for an SELECT that return 3 or less calls to the callback > function, it would work fine. Thus, it runs into trouble apparently when it > is about to call the callback function for the fourth time in a same > sqlite3_exec.
> test.exe: WinMain( ) + 71 > sqlite3.dll: sqlite3_exec( ) + 154 > sqlite3.dll: sqlite3_column_text( ) + 1A > sqlite3.dll: sqlite3_data_count( ) + AC > ntdll.dll: RtlEnterCriticalSection( ) + B Hmm, looks like a fault within SQLite's internal mutex handling. What version of sqlite is this, and did you compile it yourself? I'm wondering if it's not a compiler-related bug. ----------------------------------------------------------------------------- To unsubscribe, send email to [EMAIL PROTECTED] -----------------------------------------------------------------------------
