[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index][Old Index]
Re: dtrace + fbt provider
On 22/03/2010, at 7:22 AM, Stathis Kamperis wrote:
2010/3/21 Darran Hunt <hunt.darran%gmail.com@localhost>:
On 21/03/2010, at 4:54 PM, Stathis Kamperis wrote:
2010/3/21 Thor Lancelot Simon <tls%coyotepoint.com@localhost>:
On Sun, Mar 21, 2010 at 03:11:15AM +0200, Stathis Kamperis wrote:
With sources as of today, if I do a 'dtrace -l' I don't get 'fbt'
Is it a separate kernel module? I think it was in our local
I don't know, but I did first:
Also, I've set the various mk.conf variables + configured my
per the wiki dtrace page. And in any case, it works, it just doesn't
seem to support the 'fbt' provider.
I would appreciate any hint on how to unlock this feature, if it
You should be able to load the fbt module (modload fbt) and the sdt
after that dtrace -l will list all of the FBT probes and a few SDT
I'll update the wiki on this.
Hey Darran; first million thanks for your work on porting DTrace :)
Second, I can update the wiki page, don't waste time on such mundane
Third, I get a 100% reproducible kernel panic, every time I use an fbt
It doesn't matter which function I hook into, the system will crash
Unfortunately, I don't have a swap partition (epic fail), so I can't
set up a dump device and provide you a core.
Mind that netbsd is running as virtualbox guest in an opensolaris
Again, thanks for your work.
thanks for trying this out!
After a second look at the crash you have I think it is definitely a
bug I have detecting that there is no CTF section available for the
kernel. This happens if your /boot (secondary boot) file has not been
updated. If you copy in a new boot from <dest>/i386/usr/mdec/boot to
your root filesystem this should fix the crash. I'll work on better
detecting the problem and handling it without a crash.
Main Index |
Thread Index |