From owner-freebsd-hackers@FreeBSD.ORG  Thu Sep 13 21:14:10 2012
Return-Path: <owner-freebsd-hackers@FreeBSD.ORG>
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 22CA21065673
	for <freebsd-hackers@FreeBSD.org>; Thu, 13 Sep 2012 21:14:10 +0000 (UTC)
	(envelope-from avg@FreeBSD.org)
Received: from citadel.icyb.net.ua (citadel.icyb.net.ua [212.40.38.140])
	by mx1.freebsd.org (Postfix) with ESMTP id 66E468FC12
	for <freebsd-hackers@FreeBSD.org>; Thu, 13 Sep 2012 21:14:09 +0000 (UTC)
Received: from porto.starpoint.kiev.ua (porto-e.starpoint.kiev.ua
	[212.40.38.100])
	by citadel.icyb.net.ua (8.8.8p3/ICyb-2.3exp) with ESMTP id AAA01113;
	Fri, 14 Sep 2012 00:13:14 +0300 (EEST)
	(envelope-from avg@FreeBSD.org)
Received: from localhost ([127.0.0.1])
	by porto.starpoint.kiev.ua with esmtp (Exim 4.34 (FreeBSD))
	id 1TCGio-000BBI-3V; Fri, 14 Sep 2012 00:13:14 +0300
Message-ID: <50524C67.3040403@FreeBSD.org>
Date: Fri, 14 Sep 2012 00:13:11 +0300
From: Andriy Gapon <avg@FreeBSD.org>
User-Agent: Mozilla/5.0 (X11; FreeBSD amd64;
	rv:15.0) Gecko/20120901 Thunderbird/15.0
MIME-Version: 1.0
To: Mark Felder <feld@feld.me>
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>
	<op.wkla2ksa34t2sn@tech304>
In-Reply-To: <op.wkla2ksa34t2sn@tech304>
X-Enigmail-Version: 1.4.3
Content-Type: text/plain; charset=UTF-8
Content-Transfer-Encoding: 7bit
Cc: freebsd-hackers@FreeBSD.org, Kurt Lidl <lidl@pix.net>
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
	<freebsd-hackers.freebsd.org>
List-Unsubscribe: <http://lists.freebsd.org/mailman/listinfo/freebsd-hackers>, 
	<mailto:freebsd-hackers-request@freebsd.org?subject=unsubscribe>
List-Archive: <http://lists.freebsd.org/pipermail/freebsd-hackers>
List-Post: <mailto:freebsd-hackers@freebsd.org>
List-Help: <mailto:freebsd-hackers-request@freebsd.org?subject=help>
List-Subscribe: <http://lists.freebsd.org/mailman/listinfo/freebsd-hackers>,
	<mailto:freebsd-hackers-request@freebsd.org?subject=subscribe>
X-List-Received-Date: Thu, 13 Sep 2012 21:14:10 -0000

on 13/09/2012 22:57 Mark Felder said the following:
> 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 :-(

No, gdb stub is for debugging what is running inside the VM.
E.g. look here for an example of how to do that with qemu:
http://andriygapon.wikispaces.com/QemuSetup
VMWare with gdb stub enabled should not be any different.

-- 
Andriy Gapon