On Fri, 24 Mar 2006 10:48:34 +0200
Kostik Belousov [EMAIL PROTECTED] wrote:
I did understand the purpose of the thread mask code in
libexec/rtld/rtld_lock.c, or, more precisely, the condition where
this code works (for the context, see the mails with same subject on
freebsd-hackers).
Look,
I do not want to jinx myself, but after back revving to FreeBSD 4.9 +
patches, the system has been up for nearly 19 days. It just seems odd that
when I moved to 4.11, it worked for maybe 14 days to 30 days without a
crash. Then the crashing would randomly occur more often until it got to a
point
在 Saturday 25 March 2006 23:07,Alexander Kabaev 写道:
The thread mask only makes sense when flags are per-thread. I meant
to use it to detect PLT recursions from locking primitives exported to
rtld by the threads library as those are not allowed and threads
implementations are required to take
In the last month or two I've seen increasing occurrences of programs
refusing keyboard input after they've been running for a while
(between hours and days). They still respond to the mouse. At first
I thought it was hardware, but it happens on a number of different
machines, and only with
[ CC'd to hackers only ]
On Sun, Mar 26, 2006 at 05:50:09PM +1030, Greg 'groggy' Lehey wrote:
In the last month or two I've seen increasing occurrences of programs
refusing keyboard input after they've been running for a while
(between hours and days). They still respond to the mouse. At
Greg 'groggy' Lehey wrote:
In the last month or two I've seen increasing occurrences of programs
refusing keyboard input after they've been running for a while
(between hours and days). They still respond to the mouse. At first
I thought it was hardware, but it happens on a number of different
6 matches
Mail list logo