OSDev.org

This is the first time my OS has truly gone screwed up....

[img]
http://img402.imageshack.us/img402/6258 ... 107134.png
[/img]

I have a feeling it was very happy about that...

Bochs console says

<Numbers>[CPU0 ]BOUND_GdMa: Fails bounds test

Unkn0wn1 wrote:[CPU0 ]BOUND_GdMa: Fails bounds test

That's usually not your code that's executing.

And because it needs to be said again: http://catb.org/~esr/jargon/html/M/McQuary-limit.html <- fix that bug too.

Done........

After changing the paging model, this is what happened. The text in white at the bottom should say 'Panic!' - well, at least the panic handler was there when needed

Couple of oopses in this screenshot:



1. It appears I've gone and killed my root window and those screen regions aren't being redrawn.
2. Terminal has no way to report its size, and ls is assuming it's running in a full screen terminal.
3. It also looks like I've broken a lock somewhere in the kernel, 'cause that `view` application isn't starting (it's a simple bitmap viewer). Further attempts to open anything also froze their processes.

1 and 2 are non-issues (I accidentally hit the 'kill window' shortcut twice, and the terminal not reporting it's size is simply a missing feature). 3 scares me a bit, though.

Thumbs up for Lain there. : )

Not as bad as most people's, but still strange, especially since this is the first time something has bugged on the screen rather than internally.

Ziddia wrote:Not as bad as most people's, but still strange, especially since this is the first time something has bugged on the screen rather than internally.

And one more before I go to sleep. Got my segments out of order, and this happened trying to fix it:

Make sure your stack isn't corrupted.

VolTeK wrote:Make sure your stack isn't corrupted.

Pretty sure I fixed it.

Ziddia wrote:

VolTeK wrote:Make sure your stack isn't corrupted.

Pretty sure I fixed it.

what was the bug ?

Mozo40 wrote:

Ziddia wrote:

VolTeK wrote:Make sure your stack isn't corrupted.

Pretty sure I fixed it.

what was the bug ?

Memory segments got messed up when I jumped from my bootsector to another file. It broke my string printing routine.

I think I will laugh off of myself after fixing this, but this is result of first attempt to VBE mode string printing:

http://i.imgur.com/NdB9G.png (1600x1200, not going to embed it here...)

Not sure where I did something wrong, though.

Edit: my code was lacking one "return;" in function handling single characters, but rest was because of bug (I guess, I don't think that bug could hide somewhere in my code, checked it several times) in bochs' VBE code... it was giving me pitch for 1280x1024 in 1600x1200 mode.

Griwes wrote:I think I will laugh off of myself after fixing this, but this is result of first attempt to VBE mode string printing:

http://i.imgur.com/NdB9G.png (1600x1200, not going to embed it here...)

Not sure where I did something wrong, though.

Edit: my code was lacking one "return;" in function handling single characters, but rest was because of bug (I guess, I don't think that bug could hide somewhere in my code, checked it several times) in bochs' VBE code... it was giving me pitch for 1280x1024 in 1600x1200 mode.

How did you come across this? I'm writing a VBE driver and it seems I'm fighting Bochs more than my own code with a very similar issue to your screenshot.