Date: Wed, 1 Dec 2010 19:37:01 -0600 From: Zhihao Yuan <lichray@gmail.com> To: Brandon Gooch <jamesbrandongooch@gmail.com> Cc: freebsd-stable@freebsd.org, Andriy Gapon <avg@freebsd.org>, Jeremy Chadwick <freebsd@jdc.parodius.com> Subject: Re: Fwd: Re: Fail to use Dtrace on FreeBSD 8.1-STABLE Message-ID: <AANLkTinReeg3Xr6=553jwp5jfHuZppOd%2B0v1DC_rAEQC@mail.gmail.com> In-Reply-To: <AANLkTikcHwXWGz-hcpJfZ_cM73pgHKPgCm3bApf94gwE@mail.gmail.com> References: <20101123081244.GA38354@icarus.home.lan> <20101123082046.GA62301@compaq.yuetime> <4CEBB613.5010009@freebsd.org> <20101123131353.GA7243@icarus.home.lan> <20101123132519.GA1426@icarus.home.lan> <4CEBC155.9090706@freebsd.org> <AANLkTimsa-YM6B_272U4gjZzt1Ce05LR4sQTz_AiHJCU@mail.gmail.com> <AANLkTimb-Kijj_%2BQ2%2BxKrjtP65Zx%2BJ7rUjEP4i0HZyu6@mail.gmail.com> <20101202002734.GA84177@icarus.home.lan> <AANLkTikcHwXWGz-hcpJfZ_cM73pgHKPgCm3bApf94gwE@mail.gmail.com>
next in thread | previous in thread | raw e-mail | index | archive | help
I guess such an error has nothing to do with the difference between compilers... I assumed that you used similar KERNCONF on your two systems. So, a hypothesis is: Dtrace does not work correctly on amd64. On Wed, Dec 1, 2010 at 6:37 PM, Brandon Gooch <jamesbrandongooch@gmail.com>wrote: > On Wed, Dec 1, 2010 at 6:27 PM, Jeremy Chadwick > <freebsd@jdc.parodius.com> wrote: > > On Wed, Dec 01, 2010 at 06:22:40PM -0600, Brandon Gooch wrote: > >> On Wed, Dec 1, 2010 at 4:30 PM, Zhihao Yuan <lichray@gmail.com> wrote: > >> > OK. Let's make this more clear: anyone has a working 8-2-PRERELEASE > kernel > >> > (amd64 is preferred) with Dtrace supports, which can run the > >> > scripts/commands on the wiki? If so, please post your kernel > configurations > >> > here, thanks. > >> > >> I have an i386 system working: > >> [snip] > > > > Can you please try the command the OP originally provided? See command > > here: > > > > > http://lists.freebsd.org/pipermail/freebsd-stable/2010-November/060216.html > > d820# dtrace -lP syscall | head > ID PROVIDER MODULE FUNCTION NAME > 17 syscall syscall entry > 18 syscall syscall return > 19 syscall exit entry > 20 syscall exit return > 21 syscall fork entry > 22 syscall fork return > 23 syscall read entry > 24 syscall read return > 25 syscall write entry > > The error the OP received from the above command was pretty much > exactly what I was seeing when I attempting to use DTrace on my HEAD > system, built with clang. Same error, at least this part: > > "/usr/lib/dtrace/psinfo.d", line 88: failed to resolve type > kernel`struct thread * for identifier curthread: Unknown type name" > > I was running simply 'dtrace -l' to list all probes... > > -Brandon > -- Zhihao Yuan The best way to predict the future is to invent it.
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?AANLkTinReeg3Xr6=553jwp5jfHuZppOd%2B0v1DC_rAEQC>