From owner-freebsd-dtrace@freebsd.org Mon Feb 29 21:39:35 2016 Return-Path: Delivered-To: freebsd-dtrace@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id 54A6DAB84B4 for ; Mon, 29 Feb 2016 21:39:35 +0000 (UTC) (envelope-from hiren@strugglingcoder.info) Received: from mail.strugglingcoder.info (strugglingcoder.info [65.19.130.35]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client CN "mail.strugglingcoder.info", Issuer "mail.strugglingcoder.info" (not verified)) by mx1.freebsd.org (Postfix) with ESMTPS id 49DF21899; Mon, 29 Feb 2016 21:39:34 +0000 (UTC) (envelope-from hiren@strugglingcoder.info) Received: from localhost (unknown [10.1.1.3]) (Authenticated sender: hiren@strugglingcoder.info) by mail.strugglingcoder.info (Postfix) with ESMTPA id D1BF3110D91; Mon, 29 Feb 2016 13:39:33 -0800 (PST) Date: Mon, 29 Feb 2016 13:39:33 -0800 From: hiren panchasara To: freebsd-dtrace@freebsd.org Cc: sbruno@FreeBSD.org Subject: Functions not getting picked up by dtrace Message-ID: <20160229213933.GE82027@strugglingcoder.info> MIME-Version: 1.0 Content-Type: multipart/signed; micalg=pgp-sha512; protocol="application/pgp-signature"; boundary="LiQwW4YX+w4axhAx" Content-Disposition: inline User-Agent: Mutt/1.5.23 (2014-03-12) X-BeenThere: freebsd-dtrace@freebsd.org X-Mailman-Version: 2.1.20 Precedence: list List-Id: "A discussion list for developers working on DTrace in FreeBSD." List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 29 Feb 2016 21:39:35 -0000 --LiQwW4YX+w4axhAx Content-Type: text/plain; charset=us-ascii Content-Disposition: inline I've seen this earlier with others too but this one is the latest confusing me: em_xmit() in $src/dev/e1000/if_em.c Other functions with similar signature are listed in 'dtrace -l'. Is is because of some optimization? How do I undo it for testing purposes? Cheers, Hiren --LiQwW4YX+w4axhAx Content-Type: application/pgp-signature -----BEGIN PGP SIGNATURE----- Version: GnuPG v2 iQF8BAABCgBmBQJW1LqSXxSAAAAAAC4AKGlzc3Vlci1mcHJAbm90YXRpb25zLm9w ZW5wZ3AuZmlmdGhob3JzZW1hbi5uZXRBNEUyMEZBMUQ4Nzg4RjNGMTdFNjZGMDI4 QjkyNTBFMTU2M0VERkU1AAoJEIuSUOFWPt/l4YkH/3447rAsum76cUTN14PTXJb2 nK6qXyJBK9P53u8F6eypc9tCfBOGE4JJGsseQKIcJLjpaNQan5vRXq2hvaDEMSoL fcwictIuRsdhVitnE+VYIfkFFVB/wik58uzrTVHAOmLhTE8elOba6ReR3HaoYfBS qL2lqW49jpuUzvmugxHLXNGUBsUuyH7ldRXUopmy0zrdgx8952jgdogivjEoglzP S0/rk59nviOP1TxckJ0bGLXGt4kCICyYWIq/LJQY37gAmDSn/VnPsyMaX6Vx3/Q2 oNyKkyKcBxj2a3ReMTMhHH7/pXvanQ2lb4NlB6GbxcE86KEkFpNh73f9OfnWz34= =tPSc -----END PGP SIGNATURE----- --LiQwW4YX+w4axhAx--