kldunload DIAGNOSTIC idea...

[Julian Elischer]

Poul-Henning Kamp wrote:

>In message <20040720203739.GA72252 at VARK.homeunix.com>, David Schultz writes:
>
>  
>
>>>Looking for sleep addresses inside the module might make sense too.
>>>      
>>>
>>But this is just a heuristic that may sometimes fail.  The module
>>might be holding resources or locks, it could have callbacks, etc.
>>If we're going to offer a forcible unload option, [...]
>>    
>>
>
>This has _nothing_ to do with forcible unload.
>
>Please read the subject, again if necessary.
>
>This is an idea for a debug tool which may help people properly
>debug and implement unload *in general*.
>

as such, speed wouldnot be crucial, so having an alterred version of the 
stack trace code
that walks all available stacks looking for matching addresses would be 
quite a reasonable thingto do.

>
>  
>