Date: Fri, 22 Apr 2011 08:56:06 -0700 From: Chuck Tuffli <ctuffli@gmail.com> To: Andriy Gapon <avg@freebsd.org> Cc: freebsd-hackers@freebsd.org Subject: Re: no KLD symbols in dtrace? Message-ID: <BANLkTi=7xxbj6JP6Z7ibG7mKoDE4vuxNiA@mail.gmail.com> In-Reply-To: <4DB1A25F.8040700@FreeBSD.org> References: <BANLkTi=iDhVTsdZLrFy6JohSRBexAhWyJA@mail.gmail.com> <20110421221611.7f52ca98@kan.dnsalias.net> <BANLkTikrdkR%2BuwcBGMkCAsfEXwc%2BYtoF7w@mail.gmail.com> <20110422112444.0e423a80@kan.dnsalias.net> <4DB1A25F.8040700@FreeBSD.org>
next in thread | previous in thread | raw e-mail | index | archive | help
On Fri, Apr 22, 2011 at 8:44 AM, Andriy Gapon <avg@freebsd.org> wrote:
> on 22/04/2011 18:24 Alexander Kabaev said the following:
>> Do ctfdump -tf on your kld and verify that what it outputs actually
>> makes sense. Do kldload and see if fbt provider knows about your module
>> and functions. There is nothing else special that I can think off.
The ctfdump looks correct and
dtrace -ln "fbt::ocs_*:"
shows the kld's function names
>> Maybe make sure that you compile your sources with -g in the first
>> place? DWARF debug info is what CTF generation utils use to figure out
>> types and function prototypes.
OK
> Also, dtrace process needs to access the module file for address-to-name translation.
Hmm ... I'm building this module out of tree. Where does dtrace look
for modules?
---chuck
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?BANLkTi=7xxbj6JP6Z7ibG7mKoDE4vuxNiA>