Re: dtrace vs module unloading
On Jan 27, 2013, at 07:24 , Andriy Gapon a...@freebsd.org wrote: It seems that FreeBSD DTrace currently does not track module loading / unloading at all. dtrace_module_loaded/dtrace_module_unloaded are both under ifdef sun. I think that this is a root cause of e.g. fbt probes for some functions remaining after a module that provides the functions is unloaded. It looks like currently we do not post any event when a module gets loaded / unloaded. Perhaps this is one of the factors in current situation. OTOH, in Solaris they just have some dtrace hooks in the form of function pointers directly in the module handling code (equivalent of our kern_linker). Hrm, sounds like a bug more than anythign else. I don't know enough yet to say how to solve this but if you want to track this you're welcome to create a PR and assign it to me. Best, George ___ freebsd-hackers@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-hackers To unsubscribe, send any mail to freebsd-hackers-unsubscr...@freebsd.org
dtrace vs module unloading
It seems that FreeBSD DTrace currently does not track module loading / unloading at all. dtrace_module_loaded/dtrace_module_unloaded are both under ifdef sun. I think that this is a root cause of e.g. fbt probes for some functions remaining after a module that provides the functions is unloaded. It looks like currently we do not post any event when a module gets loaded / unloaded. Perhaps this is one of the factors in current situation. OTOH, in Solaris they just have some dtrace hooks in the form of function pointers directly in the module handling code (equivalent of our kern_linker). -- Andriy Gapon ___ freebsd-hackers@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-hackers To unsubscribe, send any mail to freebsd-hackers-unsubscr...@freebsd.org
Re: dtrace vs module unloading
On Sun, Jan 27, 2013 at 7:24 AM, Andriy Gapon a...@freebsd.org wrote: It seems that FreeBSD DTrace currently does not track module loading / unloading at all. dtrace_module_loaded/dtrace_module_unloaded are both under ifdef sun. I think that this is a root cause of e.g. fbt probes for some functions remaining after a module that provides the functions is unloaded. It looks like currently we do not post any event when a module gets loaded / unloaded. Perhaps this is one of the factors in current situation. OTOH, in Solaris they just have some dtrace hooks in the form of function pointers directly in the module handling code (equivalent of our kern_linker). I have a PR in about this. I haven't had a chance to look into fixing it myself. ___ freebsd-hackers@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-hackers To unsubscribe, send any mail to freebsd-hackers-unsubscr...@freebsd.org
