Writing your own Kernel Debugger (and using Windows)

Question about which tools to use, bugs, the best way to implement a function, etc should go here. Don't forget to see if your question is answered in the wiki first! When in doubt post here.
nexos
Member
Member
Posts: 1081
Joined: Tue Feb 18, 2020 3:29 pm
Libera.chat IRC: nexos

Re: Writing your own Kernel Debugger (and using Windows)

Post by nexos »

bzt wrote:Of course I have. MSVC likes to use its own defines instead of the standard ones. But to gave you an exact example within OSDev realm, you don't have stdint.h neither the uint*_t defines in an UEFI environment
Well, MS is MS, and they do there own thing. But, for UEFI, we have UINT8, UINT16, and so on. A simple ifdef / define in stdint.h would fix the problem

As for iced, its professional quality. It'll have some extra stuff in it. I don't see the problem with dependencies (so long as the build system wraps them up). What I am against is unnecessary bloat, and I won't make the call on Rust or iced yet, as I have never used them :)

As a rule of thumb, I always use the language which I notice the least, and lets me code. C is that language for me. Rust looks appealing, however, due to its speed.
"How did you do this?"
"It's very simple — you read the protocol and write the code." - Bill Joy
Projects: NexNix | libnex | nnpkg
Post Reply