From owner-freebsd-stable@FreeBSD.ORG Tue Aug 2 21:03:56 2011 Return-Path: Delivered-To: freebsd-stable@FreeBSD.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 6D4DA106566C for ; Tue, 2 Aug 2011 21:03:56 +0000 (UTC) (envelope-from avg@FreeBSD.org) Received: from citadel.icyb.net.ua (citadel.icyb.net.ua [212.40.38.140]) by mx1.freebsd.org (Postfix) with ESMTP id AB86E8FC16 for ; Tue, 2 Aug 2011 21:03:55 +0000 (UTC) Received: from porto.starpoint.kiev.ua (porto-e.starpoint.kiev.ua [212.40.38.100]) by citadel.icyb.net.ua (8.8.8p3/ICyb-2.3exp) with ESMTP id AAA27488; Wed, 03 Aug 2011 00:03:52 +0300 (EEST) (envelope-from avg@FreeBSD.org) Received: from localhost ([127.0.0.1]) by porto.starpoint.kiev.ua with esmtp (Exim 4.34 (FreeBSD)) id 1QoM7z-000I1B-Q6; Wed, 03 Aug 2011 00:03:51 +0300 Message-ID: <4E386636.2000507@FreeBSD.org> Date: Wed, 03 Aug 2011 00:03:50 +0300 From: Andriy Gapon User-Agent: Mozilla/5.0 (X11; FreeBSD amd64; rv:5.0) Gecko/20110706 Thunderbird/5.0 MIME-Version: 1.0 To: maestro something References: <4E2E9F60.1060808@FreeBSD.org> <4E33B7CF.90200@FreeBSD.org> <4E344D15.1040508@FreeBSD.org> <20110730192646.GC17489@deviant.kiev.zoral.com.ua> In-Reply-To: X-Enigmail-Version: 1.2pre Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 7bit Cc: Kostik Belousov , freebsd-stable@FreeBSD.org Subject: Re: dtrace ustack kernel panic X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 02 Aug 2011 21:03:56 -0000 on 02/08/2011 20:46 maestro something said the following: > Hi, > > just finished installing FreeBSD-9BETA1 and recompiling the kernel with dtrace. > > This is even worse, I have the same behavior as mentioned here: > http://freebsd.1045724.n5.nabble.com/bin-158431-dtrace-crash-in-dt-proc-lookup-when-attaching-to-PID-assert-dpr-NULL-tt4535367.html#none Kind of a mentoring note: it would be much shorter and much more useful to paste "PR 158431" or, even better, an http URL to the said PR in FreeBSD PR DB web interface. I know, I know, it's really Google to blame, right? :-) > i.e., dtrace regardless of whether with or without any probes just quits with > the following error message > > Assertion failed: (dpr != NULL), file > /usr/src/cddl/lib/libdtrace/../../../cddl/contrib/opensolaris/lib/libdtrace/common/dt_proc.c, > line 751. > > that's inside dt_proc_lookup() > > I think I have to give up on ustack(), too bad Or maybe you still have a chance to help us here, maybe it will even help you in the long term. It would be good if you pasted a little bit more of the output that you got. Please note that in that PR the (meaningful) output starts with: dtrace: no probes specified I.e. it starts with what dtrace considers to be a fatal condition. I tried to run dtruss (as you did) and I got this pre-amble before the assertion: [some dtrace script body] : probe description proc:::exit does not match any probes I guess that in my case I got it because my userland was not compiled with CTF support. Not sure about yours... Of course, it's still rather bad that dtrace crashes when it prematurely exits. But maybe it doesn't crash in the correct environment... I don't know. -- Andriy Gapon