Hi Eric,

Hi, I think you can indeed introduce a compile time option like the DOSEMU
one (which makes put_console send output to int e6 function 13) to get
output to Bochs / QEmu specific interfaces.

How should I implement the outp function to write to the port - write Open Watcom inline assembly and a separate ASM version for Turbo C, or somehow extract this function from the Run-Time Library? I have no idea how to do the latter.

On the other hand, you can just use DOSEMU :-).

Not under Windows! :) Unless I am mistaken! I checked the dosemu.org website so am fairly certain of avoiding embarassment here :)

I really recommend to use Bochs and the built-in debugger of Bochs for
kernel debugging. Make sure you have a local copy of the kernel sources
and of Ralf Brown's Interrupt List around, then you should really be able
to understand things happening in the kernel very well after a while.

I did a bit of that and had some success. I would like source-level debugging though. Perhaps I can get Emacs to launch bochsdbg (crashes under Windows XP for me right now) and write some elisp to bring up the appropriate source file for the current CS:IP, like GUD but with more intelligence, i.e. it would need to look up symbol tables to figure out which listing file to open, etc. I have written elisp like this before but it didn't have to do symbol table lookups.

Regards,
David




-------------------------------------------------------
SF.Net email is sponsored by: Discover Easy Linux Migration Strategies
from IBM. Find simple to follow Roadmaps, straightforward articles,
informative Webcasts and more! Get everything you need to get up to
speed, fast. http://ads.osdn.com/?ad_id=7477&alloc_id=16492&op=click
_______________________________________________
Freedos-kernel mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/freedos-kernel

Reply via email to