Hi Roger Your point about the preprocessor definitions is well-taken - I use them to optimize for my environment but they are not pertinent to the ticket. I recompiled sqlite3.c without all the definitions mentioned in the ticket (except -DSQLITE_OS_UNIX=1) and was still able to reproduce the error with my test code.
Could you point me to the test case you referred to? Cheers, Dave. -----Original Message----- From: Roger Binns [mailto:rog...@rogerbinns.com] Sent: Mon 10/19/2009 9:05 PM To: General Discussion of SQLite Database Subject: Re: [sqlite] Ticket 3810: SQLITE_ERROR on concurrent CREATE TEMP TRIGGER and sqlite3_close() -----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 Dave Toll wrote: > The race condition described in http://www.sqlite.org/cvstrac/tktview?tn=3810 > is > still present in SQLite 3.6.19 (amalgamation version running on Linux) My biggest problem with the ticket is the huge list of omits and other definitions at the bottom. Are they really necessary and pertinent to the ticket? They definitely shouldn't be used with the amalgamation. One of the checkins is a test case for the test suite. Perhaps supplying an improved test case would also help a lot, and prevent a regression in the future. Roger -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.9 (GNU/Linux) Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org iEYEARECAAYFAkrcxnMACgkQmOOfHg372QSjTACffDE0K7pWwlyiVZx8Kl7GeVJ2 hVUAoKuBI7uN5x14opprsvrrML0fG8Ly =oRps -----END PGP SIGNATURE-----
_______________________________________________ sqlite-users mailing list sqlite-users@sqlite.org http://sqlite.org:8080/cgi-bin/mailman/listinfo/sqlite-users
