OSDev.org

Octocontrabass wrote: That's a triple fault. The QEMU interrupt log may be useful for finding the problem.

I have attached the log below.

Octocontrabass wrote: If you see this warning, your code is broken. Fix this warning before you try to debug anything.

I have fixed this issue.

Your IDT is invalid because this struct is wrong.

Octocontrabass wrote:Your IDT is invalid because this struct is wrong.

What would be the correct way to write the struct? I'm using the one from here.

zap8600 wrote:I'm using the one from here.

Your struct does not match that struct.

Octocontrabass wrote: Your struct does not match that struct.

I need to modify ist to be uint8_t and zero to be uint32_t, I believe. I've done that, but it still isn't working.

Does it change the exceptions that lead up to the triple fault?

Octocontrabass wrote:Does it change the exceptions that lead up to the triple fault?

I believe you are taking about the check_exceptions. No, it doesn't.

In that case, there are probably other IDT issues.

What is the significance of the first parameter to idt_set_gate?

Octocontrabass wrote:In that case, there are probably other IDT issues.

What is the significance of the first parameter to idt_set_gate?

I had forgotten about that argument. It was for writing the data to that IDT entry. I've fixed it, but the exceptions haven't changed.

Has anything in the interrupt log changed?

Octocontrabass wrote:Has anything in the interrupt log changed?

Some things have changed. I put the log from an earlier test and the most recent log through diff. I don't think much changes, though. I'll attach the most recent QEMU log and the diff log.

Reply for need more explanation (Compiling in Windows is easier):

Well, for all the kernel, the drivers and libraries, this is my command line : I don't have to makefile, linker.ld and all this complicated stuff.

UEFI is just like a library, you can type any function you need at google and it will show, everything is easily setup.


Hey, do you still have the compiling issues ?

The error code has changed. This error code indicates a problem loading a segment descriptor from the GDT.

Maybe the selector in your IDT doesn't correspond to a valid code segment in your GDT. I don't see where or how your GDT is set up, though.

Octocontrabass wrote:

Code: Select all

     1: v=0d e=0008

The error code has changed. This error code indicates a problem loading a segment descriptor from the GDT.

Maybe the selector in your IDT doesn't correspond to a valid code segment in your GDT. I don't see where or how your GDT is set up, though.

I was trying to use the GDT set up by Limine. Should I make my own GDT?

Limine provides a GDT you can use temporarily. You'll need to set up your own GDT at some point, though.