From owner-freebsd-current Fri Mar 31 10: 0:45 2000 Delivered-To: freebsd-current@freebsd.org Received: from InterJet.elischer.org (c421509-a.pinol1.sfba.home.com [24.7.86.9]) by hub.freebsd.org (Postfix) with ESMTP id 1836037BCC7 for ; Fri, 31 Mar 2000 10:00:42 -0800 (PST) (envelope-from julian@elischer.org) Received: from InterJet.elischer.org (InterJet.elischer.org [192.168.1.1]) by InterJet.elischer.org (8.9.1a/8.9.1) with ESMTP id KAA23565 for ; Fri, 31 Mar 2000 10:00:41 -0800 (PST) Date: Fri, 31 Mar 2000 10:00:40 -0800 (PST) From: Julian Elischer To: current@freebsd.org Subject: Neat kernel development environment. Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG I have just managed to get the following going: By writing a device driver that is two terminals back-to-back, and configuring vmware to map one of the virtual ttys over the 'null-modem' device, and then running a kernel configured with the console on com1 and the gdb port on com2, (in the virtual machine in vmware) I can on a single machine run a test system, allow it to run the vmware X server, and at the same time have access to the console, AND be able to single step it under xxdgb or DDB depending on the task. Thus no need to have that second machine for debugging.. :-) It's amazing to see on the same X screen, 1/ The xserver of the virtual BSD box 2/ the console in another window, (which can be sent into DDB if needed) 3/ a 3rd window running xxgdb, single stepping the kernel with source and setting breakpoints etc. 4/ some othe rwindow on the host system, completely unaffected. I'll try get a screenshot. (And yes I did buy a vmware licence) Julian To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message