User:Bellezzasolo/IDT problems: Difference between revisions
Jump to navigation
Jump to search
Content added Content deleted
m (Better formatting) |
|||
| Line 8: | Line 8: | ||
== My problem == |
== My problem == |
||
Please note before you give me GCC specific adivce I have a slightly unusual setup. My setup is MS VC++ 2010 Express SP1 with the [Updated] Windows SDK, enabling 64 bit development. I use a separate assembly layer. |
Please note before you give me GCC specific adivce I have a slightly unusual setup. My setup is MS VC++ 2010 Express SP1 with the [Updated] Windows SDK, enabling 64 bit development. I use a separate assembly layer. |
||
Now you understand the environment, this is the bochs output |
|||
<pre> |
|||
interrupt(): not accessible or not code segment cs = 0x0008 |
|||
interrupt(): gate descriptor not vaolid sys seg vector = 0x0d |
|||
</pre> |
|||
== Related links == |
== Related links == |
||
Revision as of 22:30, 4 February 2012
Problems with IDTs
Many of us while OS dev'ing will encounter a problem with IDT's. I won't pretend to be an IDT agony aunt - in fact I'm in trouble myself. That is why I created this page - a wiki page you can easily access that's in a nice format. Introduction aside, I'll outline the first IDT problem this page has seen.
Feel free to add content, this is forum style
My problem
Please note before you give me GCC specific adivce I have a slightly unusual setup. My setup is MS VC++ 2010 Express SP1 with the [Updated] Windows SDK, enabling 64 bit development. I use a separate assembly layer.
Now you understand the environment, this is the bochs output
interrupt(): not accessible or not code segment cs = 0x0008 interrupt(): gate descriptor not vaolid sys seg vector = 0x0d