From owner-freebsd-hackers@FreeBSD.ORG Wed Mar 30 00:58:42 2011 Return-Path: Delivered-To: freebsd-hackers@freebsd.org Received: by hub.freebsd.org (Postfix, from userid 1233) id E52B41065674; Wed, 30 Mar 2011 00:58:42 +0000 (UTC) Date: Wed, 30 Mar 2011 00:58:42 +0000 From: Alexander Best To: freebsd-hackers@freebsd.org Message-ID: <20110330005842.GA58153@freebsd.org> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline Subject: dtrace's hotkernel script reports a memory location (0xffffffff80) instead of a function name X-BeenThere: freebsd-hackers@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Technical Discussions relating to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 30 Mar 2011 00:58:43 -0000 hi there, while running the hotkernel dtrace script from DTraceToolkit-0.99 i noticed the following: [...] kernel`sopoll_generic 60 0.1% kernel`bcopy 80 0.2% kernel`uma_zalloc_arg 100 0.2% kernel`selrecord 100 0.2% kernel`__curthread 110 0.2% kernel`syscallenter 120 0.2% kernel`fget_unlocked 130 0.3% kernel`0xffffffff80 140 0.3% kernel`copyin 190 0.4% kernel`copyout 220 0.4% kernel`inl 491 1.0% kernel`atomic_cmpset_long 570 1.1% kernel`write_rflags 652 1.3% kernel`ia32_pause 1211 2.4% kernel`cpu_mwait 1610 3.2% kernel`sched_idletd 1900 3.8% kernel`acpi_cpu_c1 40284 80.3% i talked to a few people on #bsddev, but nobody could tell me what 0xffffffff80 was refering to. kgdb(1) reports "Error accessing memory address 0xffffffff80: Bad address" for that location. any idea? -- a13x