* Marc Lehmann: > Unfortunately, the database was recreated in the meantime, "fixing" the > problem (the db utilities cna read the newly created environment), so I > have to work from past knowledge on this problem.
Since DB_ENV->set_thread_count is just a minor optimization, maybe you can get rid of it? In that case, no further debugging would be necessary. -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
