thanks very much!
On Mon, Jun 30, 2008 at 4:52 PM, D. Richard Hipp <[EMAIL PROTECTED]> wrote:
>
> >
> >
> > It is not a bug because sqlite3FaultEndBenign() is used during testing
> > only. And the tests in which this function are used only run a single
> > thread.
> >
>
>
> Recompile with -DSQLI
>
>
> It is not a bug because sqlite3FaultEndBenign() is used during testing
> only. And the tests in which this function are used only run a single
> thread.
>
Recompile with -DSQLITE_OMIT_BUILTIN_TEST=1 to completely disable the
EndBenign() function and its friends. Or omit the -DSQLITE_DE
On Jun 30, 2008, at 5:41 PM, Andrew de los Reyes wrote:
>
> I added some logging to investigate how this happens, and found
> that sqlite3FaultBeginBenign() and sqlite3FaultEndBenign() are being
> called
> with -1 as the only argument by many threads simultaneously.
>
> I added code to log entra
Hi, I think I may have discovered a bug in SQLite3. It is a timing bug that
is easily reproduced with my (unfortunately proprietary) code. I'll try to
describe the situation as best as possible. This is using SQLite source
from http://www.sqlite.org/sqlite-source-3_5_9.zip running on Mac OS X 10.5
4 matches
Mail list logo