From owner-freebsd-emulation  Thu Aug  7 16:51:19 1997
Return-Path: <owner-freebsd-emulation>
Received: (from root@localhost)
          by hub.freebsd.org (8.8.5/8.8.5) id QAA07893
          for emulation-outgoing; Thu, 7 Aug 1997 16:51:19 -0700 (PDT)
Received: from whqvax.picker.com (whqvax.picker.com [144.54.1.1])
          by hub.freebsd.org (8.8.5/8.8.5) with SMTP id QAA07884
          for <emulation@freebsd.org>; Thu, 7 Aug 1997 16:51:16 -0700 (PDT)
Received: from ct.picker.com by whqvax.picker.com with SMTP;
          Thu, 7 Aug 1997 19:50:32 -0400 (EDT)
Received: from elmer.ct.picker.com ([144.54.57.34]) by ct.picker.com (4.1/SMI-4.1)
	id AA02480; Thu, 7 Aug 97 19:50:30 EDT
Received: by elmer.ct.picker.com (SMI-8.6/SMI-SVR4)
	id TAA04512; Thu, 7 Aug 1997 19:47:56 -0400
Message-Id: <19970807194755.37948@ct.picker.com>
Date: Thu, 7 Aug 1997 19:47:55 -0400
From: Randall Hopper <rhh@ct.picker.com>
To: "Pedro Giffuni S," <pgiffuni@fps.biblos.unal.edu.co>
Cc: emulation@freebsd.org
Subject: Re: Fun with DOSCMD (was Re: modifying boot mgrs FROM FREEBSD)
References: <19970806075054.63235@ct.picker.com> <199708061320.WAA08867@genesis.atrad.adelaide.edu.au> <19970806220031.07191@ct.picker.com> <33EA058A.42B9@fps.biblos.unal.edu.co>
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
X-Mailer: Mutt 0.76
In-Reply-To: <33EA058A.42B9@fps.biblos.unal.edu.co>; from Pedro Giffuni S, on Thu, Aug 07, 1997 at 10:28:31AM -0700
Sender: owner-freebsd-emulation@freebsd.org
X-Loop: FreeBSD.org
Precedence: bulk

Pedro Giffuni S,:
 |Randall Hopper wrote:
 |> 
 |> I also need to figure out how to run doscmd in gdb.  I rebuild libkvm and
 |> gdb for the new kernel, so that's done.  But I'm not sure how to "hook in"
 |> and set breakpoints inside doscmd.kernel after its read and control is
 |> transfered to it by doscmd.  I played with the .gdbinit in the pkg but no
 |> luck.
 |> 
 |I think this is not really necessary: doscmd has a debugging option that
 |generates more information for developers, but usually the on-line
 |messages are sufficient to know what is missing.

Ok.  Mostly I just wanted to step through some of it to help get a faster
line on how the internals work.  I figured it'd be a easier than picking
through the source and printfs.

Is there a rough architecture overview or some notes/scribbles lying around
anywhere on-line that might give someone a head start with this?

Thanks,

Randall