[...]
>I have been thinking along the same lines. I have just been playing with
>the debugger and it could do with some tweaks.
>
>My first request would be that simply pressing return in the debugger
>repeats the last command. This makes it much easier to step through code.
>
>Secondly, a sorted version of the kernel system map and some ELKS specific
>code could be used to give useful about where the code is currently,
>what the stack backtrace is, and what data the current instruction is
>accessing, as well as the ability to browse and modify the data segment.
>
>Are you interested in coding any of this stuff? I would enjoy doing it
>myself, but I am trying to discipline myself to sticking to writing
>kernel code at the moment.
Well, I would if I didn't currently have a million-and-one things on my plate
already (some of them involving RL). It's frightening the way my spare time
has been disappearing recently...
So I'm afraid I'm going to have to pass on this one. I will say that pcemu is
quite well-written and designed; it was the piece of code I cut my C teeth on
(when I added the X menu, better floppy support, etc). It shouldn't be hard to
extend. Are there any takers out there?
--
+- David Given ---------------McQ-+
| Work: [EMAIL PROTECTED] | If you want to surf the Information
| Play: [EMAIL PROTECTED] | Superhighway, be prepared to be run over.
+- http://wired.st-and.ac.uk/~dg -+
