Date: Tue, 8 May 2001 18:41:54 +0200 From: Alexander Langer <alex@big.endian.de> To: Dag-Erling Smorgrav <des@ofug.org> Cc: Trevor Johnson <trevor@jpj.net>, Robert Clark <res03db2@gte.net>, Technical Information <tech_info@threespace.com>, FreeBSD Chat <chat@FreeBSD.ORG> Subject: Re: vmware anyone? Message-ID: <20010508184154.A29236@zerogravity.kawo2.rwth-aachen.d> In-Reply-To: <xzpoftjz69j.fsf@flood.ping.uio.no>; from des@ofug.org on Thu, Apr 26, 2001 at 11:43:36PM %2B0200 References: <20010425202447.A441@darkstar.gte.net> <20010426124247.Z16200-100000@blues.jpj.net> <20010426193350.A16407@cichlids.cichlids.com> <xzpoftjz69j.fsf@flood.ping.uio.no>
next in thread | previous in thread | raw e-mail | index | archive | help
Thus spake Dag-Erling Smorgrav (des@ofug.org): > > Yes, but it still doesn't work. The kernel module is ok, but the > > monitor-code from the plex86 folks does produce a fault in some > > assembler code that is written by hand, and I'm not able to fix that. > Do you have a trace and a listing of the code surrounding the fault? Hi! I tried it several times now. The kernel is hard-locked when that happens, i.e. it won't produce a kernel dump. If I compile a kernel with DDB support, I can do "trace", but only until an exit of a fork() call, so this doesn't help either. I have the assembler in-kernel code, that is executed right after a fault, but manually initialing a kernel break at this point (e.g. by a halt point) immediately reboots the kernel. Note that the said fault is a plex86 specific fault, which happens while monitoring the guest os, and not a FreeBSD kernel fault. Thus I'm unable to find the code surrounding the fault, I'm sorry. Alex -- cat: /home/alex/.sig: No such file or directory To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-chat" in the body of the message
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?20010508184154.A29236>