On Mon, 3 Nov 2003, John Baldwin wrote:
> On 01-Nov-2003 Soren Schmidt wrote:
> > It seems Sean Chittenden wrote:
> >> Howdy. I'm not sure if this is a ULE bug or a KSE bug, or both, but,
> >> for those interested (this is using ule 1.67, rebuilding world now),
> >> here's my stack. I couldn't f
It seems John Baldwin wrote:
>
> On 01-Nov-2003 Soren Schmidt wrote:
> > It seems Sean Chittenden wrote:
> >> Howdy. I'm not sure if this is a ULE bug or a KSE bug, or both, but,
> >> for those interested (this is using ule 1.67, rebuilding world now),
> >> here's my stack. I couldn't figure out
On 01-Nov-2003 Soren Schmidt wrote:
> It seems Sean Chittenden wrote:
>> Howdy. I'm not sure if this is a ULE bug or a KSE bug, or both, but,
>> for those interested (this is using ule 1.67, rebuilding world now),
>> here's my stack. I couldn't figure out where td was being set to
>> NULL. :( O
It seems Sean Chittenden wrote:
> Howdy. I'm not sure if this is a ULE bug or a KSE bug, or both, but,
> for those interested (this is using ule 1.67, rebuilding world now),
> here's my stack. I couldn't figure out where td was being set to
> NULL. :( Oh! Where is TD_SET_LOCK defined? egrep -r
> Howdy. I'm not sure if this is a ULE bug or a KSE bug, or both, but,
> for those interested (this is using ule 1.67, rebuilding world now),
> here's my stack. I couldn't figure out where td was being set to
> NULL. :( Oh! Where is TD_SET_LOCK defined? egrep -r didn't turn up
> anything. -sc
Howdy. I'm not sure if this is a ULE bug or a KSE bug, or both, but,
for those interested (this is using ule 1.67, rebuilding world now),
here's my stack. I couldn't figure out where td was being set to
NULL. :( Oh! Where is TD_SET_LOCK defined? egrep -r didn't turn up
anything. -sc
(kgdb) b
