On Thu, 2005-06-16 at 15:25 -0400, Christopher R. Palmer wrote:
> The new misuse tests that were added were very helpful for identifying
> this. But, are the current behaviour (and tests) the "right" ones?
It is the only behavior that will work given the general brokenness of
posix locks and th
My problem (ticket 1272) is that I open multiple sqlite handles in one
thread and then pass the handles to other threads to perform the work.
That is:
db1 = sqlite3_open();
db2 = sqlite3_open();
pthread_create(...,db1);
pthread_create(...,db2);
While this does not appear to be disallowed by th
On Wed, 2005-06-15 at 10:05 -0400, D. Richard Hipp wrote:
> There are currently two outstanding tickets against SQLite
> for deadlocks while running multiple threads on RedHat 9.
> See
>
> http://www.sqlite.org/cvstrac/tktview?tn=1285
> http://www.sqlite.org/cvstrac/tktview?tn=1272
>
The gro
On Wed, 2005-06-15 at 12:43 -0400, Christopher R. Palmer wrote:
> I've temporarily placed the trace file at
>
> http://67.19.10.2/~crpalmer/sqlite-traking.gz
>
The file is named sqlite-trace-locking.gz. And it
did not containing the debugging information I need.
Perhaps you didn't compile with
D. Richard Hipp wrote:
On Wed, 2005-06-15 at 10:24 -0400, Christopher R. Palmer wrote:
In my case, I added printf statements to trace the fcntl calls and it was
the case that one thread did the fcntl to get the shared lock and then a
second thread attempted the fcntl to go from shared to exclu
On Wed, 2005-06-15 at 10:24 -0400, Christopher R. Palmer wrote:
> In my case, I added printf statements to trace the fcntl calls and it was
> the case that one thread did the fcntl to get the shared lock and then a
> second thread attempted the fcntl to go from shared to exclusive. This is
> wh
June 15, 2005 10:06 AM
To: sqlite-users@sqlite.org
Subject: [sqlite] Thread locking issues on RH9
There are currently two outstanding tickets against SQLite
for deadlocks while running multiple threads on RedHat 9.
See
http://www.sqlite.org/cvstrac/tktview?tn=1285
http://www.sqlite.org/cvstrac/tkt
I am the one that reported ticket 1272. Glad to hear that you are looking
into this!
In my case, I added printf statements to trace the fcntl calls and it was
the case that one thread did the fcntl to get the shared lock and then a
second thread attempted the fcntl to go from shared to exclus
There are currently two outstanding tickets against SQLite
for deadlocks while running multiple threads on RedHat 9.
See
http://www.sqlite.org/cvstrac/tktview?tn=1285
http://www.sqlite.org/cvstrac/tktview?tn=1272
I have been working closely with the group that reported
ticket #1285. I have s
9 matches
Mail list logo
