Date: Wed, 19 Sep 2012 08:09:36 -0400 From: John Baldwin <jhb@freebsd.org> To: Mark Felder <feld@feld.me> Cc: freebsd-hackers@freebsd.org, Andriy Gapon <avg@freebsd.org> Subject: Re: Please help me diagnose this crazy VMWare/FreeBSD 8.x crash Message-ID: <201209190809.36161.jhb@freebsd.org> In-Reply-To: <op.wkk0qzwj34t2sn@tech304> References: <op.wbwe9s0k34t2sn@tech304> <5051F7A0.90901@FreeBSD.org> <op.wkk0qzwj34t2sn@tech304>
next in thread | previous in thread | raw e-mail | index | archive | help
On Thursday, September 13, 2012 12:14:49 pm Mark Felder wrote: > On Thu, 13 Sep 2012 10:11:28 -0500, Andriy Gapon <avg@freebsd.org> 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
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?201209190809.36161.jhb>