OSDev.org

So in your opinion the first cause of the crash is a page fault?

We know guaranteed that the 2 exceptions causing the triple fault is a #GPF and #PF. The #PF is the most likley culprit. (Bochs tells us an 0x13 exception (#GPF) occurred that generated the triple fault and CR2 containes an address updated only by #PF)

When a #PF occurs, CR2 holds the faulting address. Go through your code and find where you are referencing this address to see exactally where the #PF occurs.

I would also check if IRQ 14 and IRQ 13 are working by manually initiating them to test it. (ie; try to force a crash by forcing them to happen to see if you get expected results). If you do, then the handlers are fine. If not, then that may be the source of the problems.

Jeko wrote:Sorry... But I'm very confused... This is the first time I debug my kernel... This is the absolutely first time that I debug something, so I need your help...
Sorry for stupid questions and similar, but I'm very ignorant about this argument.

You're thinking of Network-, (Graphic-)Devicehandling, loading shared libraries,..., but you don't know how to debug?
You should lower your aims or better you should start with something like tetris, no?
I think you're not ready for OS development.

cyr1x wrote:

Jeko wrote:Sorry... But I'm very confused... This is the first time I debug my kernel... This is the absolutely first time that I debug something, so I need your help...
Sorry for stupid questions and similar, but I'm very ignorant about this argument.

You're thinking of Network-, (Graphic-)Devicehandling, loading shared libraries,..., but you don't know how to debug?
You should lower your aims or better you should start with something like tetris, no?
I think you're not ready for OS development.

Yes, I'm developing my OS, but I don't know how to debug. But I'm learning, why I must stop OS development? I can learn...
Thank you for the help!

The problem is, you expect other people to spoon-feed you with all the answers. You will learn from that eventually, but it wastes lots of time from other people, time we can spend better.

Since you apparently lack one of the necessary skills to even do userland programming, OS development is going to be out of the question. The only reason you got so far is by taking every piece of code that was premade and put it together until it stopped working, then came here to annoy us with the resulting questions until we got fed up and gave you the answer, then you just copy-pasted that and went on like before.
Or at least, that's the reputation you've gotten over time. Having 500+ posts and not being able to fix a pagefault gives you a similar reputation to other people who don't know your history.

I agree with cyr1x that it is better to leave OS development until you have done some serious userland work. You're essentially asking us to teach you one of the basics of programming, while the rules state that you need to have these requirements before asking here.