Date: Fri, 13 Jun 2008 00:20:32 +0200 From: "Diego Depaoli" <trebestie@gmail.com> To: "John Birrell" <jb@what-creek.com>, current@freebsd.org Subject: Re: Getting started with DTrace in FreeBSD-current (a.k.a. 8) Message-ID: <83e5fb980806121520q3fa5596bu65141bf1a5fe2cb3@mail.gmail.com> In-Reply-To: <20080612215229.GA68604@what-creek.com> References: <20080611051257.GA51683@what-creek.com> <83e5fb980806121438m1e627af9vf9ab294ca56206eb@mail.gmail.com> <20080612215229.GA68604@what-creek.com>
next in thread | previous in thread | raw e-mail | index | archive | help
2008/6/12 John Birrell <jb@what-creek.com>: > On Thu, Jun 12, 2008 at 11:38:50PM +0200, Diego Depaoli wrote: >> 2008/6/11 John Birrell <jb@what-creek.com>: >> > >> > It's been a few weeks now since I committed DTrace support to current. >> >> I'm curious... impact over performances? > > DTrace is supposed to be low impact until you enable probes. Well > When you enable > probes, the impact depends on how many probes, how often they are called > and what the actions do. Sounds logic >> kern_dtrace.o(.text+0x1e0): first defined here >> ld: Warning: size of symbol `kdb_enter' changed from 34 in >> kern_dtrace.o to 70 in subr_kdb.o >> *** Error code 1 > > Try removing the #ifndef and the code it contains in kern_dtrace.c. > It looks like the kdb_enter function is always compiled in. Make kernel goes right, now I reboot. Many thanks -- Diego Depaoli
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?83e5fb980806121520q3fa5596bu65141bf1a5fe2cb3>