Date: Tue, 5 Nov 2013 21:45:49 -0500 From: Mark Johnston <markj@freebsd.org> To: John Luk <john.37@gmail.com> Cc: freebsd-dtrace@freebsd.org Subject: Re: dtrace showed matched probes but nothing in output on FreeBSD 9.1-RELEASE Message-ID: <20131106024549.GA2826@raichu> In-Reply-To: <CAHkCX6hyHfzBaHqYg0=wONphkGdDL7x-ErC5s60wK_aiczR3rA@mail.gmail.com> References: <CAHkCX6j1H4cxeb255gdH_cLop5Lv0xJABbuma%2B835gNNq-Nshg@mail.gmail.com> <20131103235936.GB15661@raichu> <CAHkCX6g1jUirMDP4T7W%2BrP6P8JV5wF-Wsa984op_HP1WftSitA@mail.gmail.com> <20131104043519.GB8007@raichu> <CAHkCX6h312PJvukGo_MNowNpENDLT=hvmXymZRsDFW%2BtzYNPug@mail.gmail.com> <CAHkCX6iT2MKMRwQDQrWLLjMXx9kiiYneT4J_qirxn1EwshmGng@mail.gmail.com> <20131104141105.GE8007@raichu> <CAHkCX6hyHfzBaHqYg0=wONphkGdDL7x-ErC5s60wK_aiczR3rA@mail.gmail.com>
next in thread | previous in thread | raw e-mail | index | archive | help
On Tue, Nov 05, 2013 at 02:47:58PM +0800, John Luk wrote: > Hi, Mark. The gdb output is included below. I'm wondering why dtrace -l can > trace all my function correctly but the D script failed. Is it because they get > the symbol table in different way? Hm, I can't reproduce the problem using your binary on a machine running head. I suspect the problem has to do with some other DTrace bugs in the kernel which have been recently fixed - there were a couple that would corrupt the state of traced programs in various ways, and it could be that inet_makeaddr() really isn't getting called as a result. You could try adding a printf or something to see if that's the case. In general there have been quite a few DTrace fixes since 9.1, so it's worth trying out newer revisions if you're interested in trying out DTrace on FreeBSD. -Mark
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?20131106024549.GA2826>