Skip site navigation (1)Skip section navigation (2)
Date:      Thu, 13 Sep 2012 14:57:46 -0500
From:      Mark Felder <feld@feld.me>
To:        Kurt Lidl <lidl@pix.net>
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:  <op.wkla2ksa34t2sn@tech304>
In-Reply-To: <20120913162815.GA1219@pix.net>
References:  <op.wbwe9s0k34t2sn@tech304> <201205311157.42909.jhb@freebsd.org> <19d73256-b7c6-417e-a051-a5faeabf219d@email.android.com> <201209121520.26337.jhb@freebsd.org> <op.wkkwu1sx34t2sn@tech304> <5051F7A0.90901@FreeBSD.org> <op.wkk0qzwj34t2sn@tech304> <20120913162815.GA1219@pix.net>

next in thread | previous in thread | raw e-mail | index | archive | help
On Thu, 13 Sep 2012 11:28:15 -0500, Kurt Lidl <lidl@pix.net> wrote:

> Isn't this what you want?
>
> http://stackframe.blogspot.com/2007/04/debugging-linux-kernels-with.html
>
> -Kurt

Interesting -- it looks like that's an option on ESX as well. The only  
question is: what do I do with that? It's going to give me the debugging  
entire VM, not the kernel inside. Without being a VMWare developer I  
imagine its data will be a bit useless :-(



Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?op.wkla2ksa34t2sn>