On 31-Dec-00 User Sja wrote:
> I don't really know my way around the kernel so I'm just guessing here:
>
> Is there a proctree lock release operation missing in kern_sig.c,
> function issignal()? There seems to be one lock operation more
> than there are release operations. I tried putting one
User Sja <[EMAIL PROTECTED]> wrote:
> I don't really know my way around the kernel so I'm just guessing here:
>
> Is there a proctree lock release operation missing in kern_sig.c,
> function issignal()? There seems to be one lock operation more
> than there are release operations. I tried putti
On Sun, 31 Dec 2000, User Sja wrote:
> I don't really know my way around the kernel so I'm just guessing here:
>
> Is there a proctree lock release operation missing in kern_sig.c,
> function issignal()? There seems to be one lock operation more
> than there are release operations. I tried putt
I don't really know my way around the kernel so I'm just guessing here:
Is there a proctree lock release operation missing in kern_sig.c,
function issignal()? There seems to be one lock operation more
than there are release operations. I tried putting one in and
now gdb doesn't hang the whole m