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) Message-ID: <19970807194755.37948@ct.picker.com> In-Reply-To: <33EA058A.42B9@fps.biblos.unal.edu.co>; from Pedro Giffuni S, on Thu, Aug 07, 1997 at 10:28:31AM -0700 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>
next in thread | previous in thread | raw e-mail | index | archive | help
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
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?19970807194755.37948>