I have completed the Global Descriptor Table now. There is no compiler or linker error and the kernel runs, but I am not sure whether the GDT is implemented right and I don't want to go on until I know. How can I test whether the GDT is alright?
errorX
How to test the GDT?
-
Combuster
- Member
- Posts: 9301
- Joined: Wed Oct 18, 2006 3:45 am
- Libera.chat IRC: [com]buster
- Location: On the balcony, where I can actually keep 1½m distance
- Contact:
Re: How to test the GDT?
tried bochs in debugger mode?
Re: How to test the GDT?
I'm using QEMU but I think there's a debugger mode, too. I'll try.
Thanks for this tip.
Thanks for this tip.
-
Troy Martin
- Member
- Posts: 1686
- Joined: Fri Apr 18, 2008 4:40 pm
- Location: Langley, Vancouver, BC, Canada
- Contact:
Re: How to test the GDT?
Welcome, errorX!
Yeah, try using a debugger in QEMU or whatever emulator you use. That helps to find issues with memory and anything loaded into memory.
I'm curious, what's your OS project? I assume you've had experience with 16-bit OS programming, since 32-bit can get hard for less experienced people (no bios calls, etc.)
Yeah, try using a debugger in QEMU or whatever emulator you use. That helps to find issues with memory and anything loaded into memory.
I'm curious, what's your OS project? I assume you've had experience with 16-bit OS programming, since 32-bit can get hard for less experienced people (no bios calls, etc.)
I wish I could add more texSolar wrote:It keeps stunning me how friendly we - as a community - are towards people who start programming "their first OS" who don't even have a solid understanding of pointers, their compiler, or how a OS is structured.
Re: How to test the GDT?
Ok, thanks for your help. I wonder, it really seems to be alright.
My OS project is really small. I've less experience, but I just write it to get this experience, trying to get as far as I can.
My OS project is really small. I've less experience, but I just write it to get this experience, trying to get as far as I can.