RE: PROCTREE_LOCK() vs. gdb hang

2000-12-31 Thread John Baldwin
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

Re: PROCTREE_LOCK() vs. gdb hang

2000-12-31 Thread Brian F. Feldman
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

Re: PROCTREE_LOCK() vs. gdb hang

2000-12-31 Thread Wesley Morgan
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

PROCTREE_LOCK() vs. gdb hang

2000-12-31 Thread User Sja
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