debug5.0problems In-Reply-To: <[EMAIL PROTECTED]> Message-ID: <[EMAIL PROTECTED]> MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII
On Tue, 26 Nov 2002, Terry Lambert wrote: > Julian Elischer wrote: > > > The answer is that "the code doesn't care what thread"; it would > > > prefer to not have to think in terms of threads at all, but if > > > you want to force it to, then it's going to think in terms of > > > "blocking contexts for the benefit of FreeBSD code it calls", > > > and nothing else. > > > > Hense the confusion as to whether to use a thread or a proc.. > > Not confusing at all. The only issue is references to the > connection structure caches proc, which uses the first thread > on the cached proc; otherwise, it uses the thread that was > passed in. Where does the passed in thread come from? Generally don't use a thread pointer other than yourself unless you have a lock on the proc structure, or the schedlock. Certainly never store it anywhere.. Particularly anywhere that may persist while you sleep in any way. -exception.. kernel threads- .. they are persistant. To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
