![]() To comments about the UEFI and ReactOS, I would think the developers would understand that and would add support. I guess it is just because I have been using Windows the longest. I want to start with Windows for some reason. Yes, it is strangely satisfying reading about and figuring out operating systems internals. It was all pretty clunky, but it was the only game in town, so I made it work. The debugging machine was another Windows NT computer running a normal kernel, but hosting the debugging tools that were hooked to the target machine via the com ports of the two machines, using a null modem cross-over wired cable. I was developing kernel mode device drivers for a machine vision SIMD array board on PCI bus, so this was about the only way I could see what was happening when my NT device driver made calls into kernel mode. The instrumented kernel allowed seeing certain things going on under the covers. Even with an instrumented kernel, developers still didn't get any Windows kernel source code, so that you could trace a call from the user mode up until it made the call into the kernel, and then it was opaque until the call returned to the user mode. It required an 'instrumented' Windows NT kernel, which was supplied in the WDK, so that it would spill its guts over a hardware serial port while running various kernel calls and during boot up. Many years ago, I had a setup as mentioned in the article you linked to. I am sure people out on the internet know and understand the answer to this question, but Steve is the exact first person that comes to mind for me. I would want to have the source code in the debugger vm and not just the disassembly. ![]() Then I realized if it is possible for React OS, it is likely to be possible with FreeDOS, Linux and maybe Windows. I been reading about OS internal and then I remembered ReactOS and I wondered if there would be a way to use a debugger in one ReactOS instance with another ReactOS/Windows/Linux instance, both in virtual machines. ![]() As virtual machines have com ports, I can’t think of a reason why this could not be done with two virtual machine no matter if they are FreeDOS, ReactOS, Windows, or Linux. I remember reading in a masm dos book a long time ago, that you could debug assembly on one computer with another computer via the com ports. I am including a link to an article for an old version of vmware workstation, but I think is should work for both vmware workstation and virtual box. I am trying to understand how to debug the contents of one virtual machine with another virtual machine or as least the host. I might end up asking on StackOverflow and reddit too, but again I feel like this is the kind of thing Steve would know and understand. Ok, I am sorry if this is not the place to ask so many questions, but I really think Steve and maybe/hopefully someone else will know the answer to this question.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |