6 Commits

Author	SHA1	Message	Date
dan	fe98f9b216	Avoid running thread1.test or thread2.test if SQLITE_MUTEX_NOOP is defined. ... FossilOrigin-Name: 532ae32ea0f5e821dac643cbc4b041c103cadfdc	2011-04-07 14:05:47 +00:00
drh	8af6c228f8	Simplify os_unix.c by removing support for LinuxThreads. Linux systems must ... either use NPTL or else not share database connections across threads. FossilOrigin-Name: e294b696ba91512b1ca5547774c51ea07b4cb5bc	2010-05-14 12:43:01 +00:00
dan	11b3879b18	Trying to open a transaction in one thread and close it in another is a misuse with LinuxThreads. Doing so may cause memory and file-descriptors to be leaked. Update an assert() and some test cases to account for this. ... FossilOrigin-Name: ef99eb57c536d82e7c19fd3d990c17793cc64a3f	2009-09-09 18:46:52 +00:00
drh	18472fa7b8	Remove the SQLITE_MUTEX_APPDEF compile-time option. The SQLITE_THREADSAFE=0 ... option always removes all mutex code. For application-defined mutexes only, use SQLITE_THREADSAFE=1 with SQLITE_MUTEX_NOOP=1. Ticket #3421. (CVS 5779) FossilOrigin-Name: 02a12eb1cfe9307c66556105a1a99d657cc01ab5	2008-10-07 15:25:48 +00:00
danielk1977	e7823cb591	Omit thread2.test if memory-management is enabled at compile time. (CVS 2975) ... FossilOrigin-Name: df91f685cacbcb3e048eaa03260b33bbcfcb321c	2006-01-18 18:33:42 +00:00
drh	64b1bea3ba	Add tests and fix bugs in the new cross-thread lock resolution code. ... When an unlock fails, do not leak file descriptors (ticket #1611). But we really ought to report SQLITE_MISUSE or some other error instead of just returning SQLITE_OK. (CVS 2945) FossilOrigin-Name: f68e05cb2be65fad43fac823b2a9c53b6d2e797d	2006-01-15 02:30:57 +00:00