From owner-freebsd-current@FreeBSD.ORG Fri Sep 11 16:40:02 2009 Return-Path: Delivered-To: freebsd-current@FreeBSD.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 0C998106566B; Fri, 11 Sep 2009 16:40:02 +0000 (UTC) (envelope-from avg@icyb.net.ua) Received: from citadel.icyb.net.ua (citadel.icyb.net.ua [212.40.38.140]) by mx1.freebsd.org (Postfix) with ESMTP id 1C5228FC13; Fri, 11 Sep 2009 16:39:59 +0000 (UTC) Received: from odyssey.starpoint.kiev.ua (alpha-e.starpoint.kiev.ua [212.40.38.101]) by citadel.icyb.net.ua (8.8.8p3/ICyb-2.3exp) with ESMTP id TAA17934; Fri, 11 Sep 2009 19:39:58 +0300 (EEST) (envelope-from avg@icyb.net.ua) Message-ID: <4AAA7D5E.5050604@icyb.net.ua> Date: Fri, 11 Sep 2009 19:39:58 +0300 From: Andriy Gapon User-Agent: Thunderbird 2.0.0.22 (X11/20090724) MIME-Version: 1.0 To: Gavin Atkinson References: <4AAA54FF.9080701@icyb.net.ua> <1252679211.31066.43.camel@buffy.york.ac.uk> <4AAA61A0.2040600@icyb.net.ua> <1252685048.31066.55.camel@buffy.york.ac.uk> In-Reply-To: <1252685048.31066.55.camel@buffy.york.ac.uk> X-Enigmail-Version: 0.95.7 Content-Type: text/plain; charset=KOI8-U Content-Transfer-Encoding: 7bit Cc: freebsd-current@FreeBSD.org Subject: Re: crashinfo issue in HEAD X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 11 Sep 2009 16:40:02 -0000 on 11/09/2009 19:04 Gavin Atkinson said the following: > > Hmm, in that case this is probably a different bug to the ones already > found, and that patch won't help. Can you recompile ps and libkvm with > debugging symbols, run it under gdb and get a backtrace? Your original > stack trace shows kvm_getprocs() calling _kvm_freeprocs(), however the > code doesn't appear to ever do this: indeed, nothing in libkvm calls > _kvm_freeprocs() directly. I tried debugging this and figured out that I am stupid - my world is at older revision than my kernel and it is couple revisions before r196990 that fixed the problem. So, sorry for the noise and big thanks! -- Andriy Gapon