From owner-freebsd-hackers@FreeBSD.ORG Wed Sep 19 12:25:10 2012 Return-Path: Delivered-To: freebsd-hackers@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id D722B1065673; Wed, 19 Sep 2012 12:25:10 +0000 (UTC) (envelope-from jhb@freebsd.org) Received: from bigwig.baldwin.cx (bigknife-pt.tunnel.tserv9.chi1.ipv6.he.net [IPv6:2001:470:1f10:75::2]) by mx1.freebsd.org (Postfix) with ESMTP id ACC5B8FC12; Wed, 19 Sep 2012 12:25:10 +0000 (UTC) Received: from jhbbsd.localnet (unknown [209.249.190.124]) by bigwig.baldwin.cx (Postfix) with ESMTPSA id CD04EB964; Wed, 19 Sep 2012 08:25:09 -0400 (EDT) From: John Baldwin To: Mark Felder Date: Wed, 19 Sep 2012 08:09:36 -0400 User-Agent: KMail/1.13.5 (FreeBSD/8.2-CBSD-20110714-p17; KDE/4.5.5; amd64; ; ) References: <5051F7A0.90901@FreeBSD.org> In-Reply-To: MIME-Version: 1.0 Content-Type: Text/Plain; charset="utf-8" Content-Transfer-Encoding: 7bit Message-Id: <201209190809.36161.jhb@freebsd.org> X-Greylist: Sender succeeded SMTP AUTH, not delayed by milter-greylist-4.2.7 (bigwig.baldwin.cx); Wed, 19 Sep 2012 08:25:09 -0400 (EDT) Cc: freebsd-hackers@freebsd.org, Andriy Gapon Subject: Re: Please help me diagnose this crazy VMWare/FreeBSD 8.x crash 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, 19 Sep 2012 12:25:10 -0000 On Thursday, September 13, 2012 12:14:49 pm Mark Felder wrote: > On Thu, 13 Sep 2012 10:11:28 -0500, Andriy Gapon wrote: > > > Just curious - does VMWare provide a remote debugger support (gdb stub)? > > I'm not aware of one. What I have been able to successfully do is break > into the debugger during the hang but the info I've posted so far has not > been relevant to anyone. I'm hoping someone on the core team will > eventually be able to follow my guide and figure out what went wrong. So the last e-mail I sent before this week I asked if you could get a crashdump from DDB? The "flswai" case you pointed to was a lock deadlock, and having a crashdump would be really helpful for figuring out which threads were deadlocked. Barring a crashdump, capturing 'ps' output from DDB would be a good first step (you can sanitize process names if you need to). However, a crashdump that you can use kgdb on will make debugging this significantly easier. -- John Baldwin