ignore the previous:
> either way fp is garbage on the stack at this point if not > KTROP_CLEAR. the uses in ktrace_common() won't fault, but the > fd_abort()s will (which is where we see the panic). > > can people see if this works ok if fp is initialised to NULL? > (either at the top of the function or preferably as an else > clause right above the call to ktrace_common(). i was looking at the fp decl in sys_fktrace() here. fp is initialised to NULL correctly in sys_ktrace(). .mrg.
