From owner-freebsd-current@FreeBSD.ORG Tue Jan 8 00:23:08 2013 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by hub.freebsd.org (Postfix) with ESMTP id A2D4FDB4 for ; Tue, 8 Jan 2013 00:23:08 +0000 (UTC) (envelope-from rysto32@gmail.com) Received: from mail-oa0-f41.google.com (mail-oa0-f41.google.com [209.85.219.41]) by mx1.freebsd.org (Postfix) with ESMTP id 738DEF55 for ; Tue, 8 Jan 2013 00:23:08 +0000 (UTC) Received: by mail-oa0-f41.google.com with SMTP id k14so18616360oag.28 for ; Mon, 07 Jan 2013 16:23:07 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:in-reply-to:references:date:message-id:subject:from:to :cc:content-type; bh=PcQWge02qfaT+toNfe1w2Ss4VqGVCXNdJPfjAceGahE=; b=sgisNitoBrNRHFFcvdRuzh8tYOxzv7WyOAgsLJdwwBGWVclbLqwF2MvC28XBdTjyXx EsGGp/eb9GQBRwXQvLlLH9OZqvuuTT28bUMt5PwTb68H9fFyUilJW3VFwElYJ2LOxXaC vmxydpPYKRIutSn0knvgHF1Tblg8rr4JXkL13txFX2noTaGqI6OvyfVy72zhRcbe0E26 huN76pMM9F1m7agnDSSQvamo55b+MVpnLZVDnMz9P/fHfqXqW0uHLuDzOHfhcOHI3QcW dy1gdIe+0LYaGBODEDmTyqPspjPHPns+bbQHJjPUUfXv22fFo09/J5+YtlZKOietWatX TguA== MIME-Version: 1.0 Received: by 10.60.171.175 with SMTP id av15mr34091285oec.75.1357604587477; Mon, 07 Jan 2013 16:23:07 -0800 (PST) Received: by 10.76.128.68 with HTTP; Mon, 7 Jan 2013 16:23:07 -0800 (PST) In-Reply-To: References: <50EB602F.9050300@delphij.net> <20130108000233.GZ82219@kib.kiev.ua> <50EB63A9.50903@delphij.net> Date: Mon, 7 Jan 2013 19:23:07 -0500 Message-ID: Subject: Re: sysctl -a causes kernel trap 12 From: Ryan Stone To: Xin LI Content-Type: text/plain; charset=ISO-8859-1 X-Content-Filtered-By: Mailman/MimeDel 2.1.14 Cc: Konstantin Belousov , FreeBSD Current X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.14 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: Tue, 08 Jan 2013 00:23:08 -0000 On Mon, Jan 7, 2013 at 7:21 PM, Ryan Stone wrote: > Have you tried dropping into the debugger by setting > debug.debugger_on_panic=1 instead of trying to generate a core? You might > have some success generating at least a backtrace. > Sigh, reading comprehension fail on my part. Try generating a core, I guess. Another think that you could do would be to annotate the sysctl code path to print the name of the sysctl that it is about to run to the console.