From owner-svn-src-head@freebsd.org Thu Apr 20 17:02:57 2017 Return-Path: Delivered-To: svn-src-head@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 A1B53D48652; Thu, 20 Apr 2017 17:02:57 +0000 (UTC) (envelope-from slw@zxy.spb.ru) Received: from zxy.spb.ru (zxy.spb.ru [195.70.199.98]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client did not present a certificate) by mx1.freebsd.org (Postfix) with ESMTPS id 5D3771F3E; Thu, 20 Apr 2017 17:02:57 +0000 (UTC) (envelope-from slw@zxy.spb.ru) Received: from slw by zxy.spb.ru with local (Exim 4.86 (FreeBSD)) (envelope-from ) id 1d1FTq-0008Uz-3c; Thu, 20 Apr 2017 20:02:54 +0300 Date: Thu, 20 Apr 2017 20:02:54 +0300 From: Slawa Olhovchenkov To: John Baldwin Cc: rgrimes@freebsd.org, Ngie Cooper , Warner Losh , Eric van Gyzen , "svn-src-head@freebsd.org" , "svn-src-all@freebsd.org" , src-committers Subject: Re: svn commit: r317094 - head/share/mk Message-ID: <20170420170253.GR70430@zxy.spb.ru> References: <201704201608.v3KG8S7J036363@pdx.rh.CN85.dnsmgr.net> <15726118.uZgJrz4zO8@ralph.baldwin.cx> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <15726118.uZgJrz4zO8@ralph.baldwin.cx> User-Agent: Mutt/1.5.24 (2015-08-30) X-SA-Exim-Connect-IP: X-SA-Exim-Mail-From: slw@zxy.spb.ru X-SA-Exim-Scanned: No (on zxy.spb.ru); SAEximRunCond expanded to false X-BeenThere: svn-src-head@freebsd.org X-Mailman-Version: 2.1.23 Precedence: list List-Id: SVN commit messages for the src tree for head/-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 20 Apr 2017 17:02:57 -0000 On Thu, Apr 20, 2017 at 09:58:10AM -0700, John Baldwin wrote: > > Well it seems it can do some rather important trivial things, like post > > mortem process kernel dumps during savecore processing helping users > > submit a kernel panic bugzilla with more than just traceback info. > > Only somewhat. You should actually try to use kgdb and compare it to the > kgdb in ports. I am don't see many difference: both do strange results, both crashed. For kernel and userland too.