flat assembler
Message board for the users of flat assembler.
Index
> OS Construction > Why does the code lead to a reset in bochs |
Author |
|
sinsi 08 Feb 2015, 09:50
CLI before LIDT
|
|||
08 Feb 2015, 09:50 |
|
l4m2 08 Feb 2015, 09:51
sinsi wrote: CLI before LIDT But I've already CLI just after starting |
|||
08 Feb 2015, 09:51 |
|
revolution 08 Feb 2015, 11:04
There is no evidence of a CLI in the code your posted. So if you say you have CLI somewhere else then the problem could also be in that somewhere else.
Post ALL the code you are using else we are just running blind wondering what you have done. |
|||
08 Feb 2015, 11:04 |
|
l4m2 08 Feb 2015, 11:54
revolution wrote: There is no evidence of a CLI in the code your posted. So if you say you have CLI somewhere else then the problem could also be in that somewhere else. Code: |
|||
08 Feb 2015, 11:54 |
|
l4m2 09 Feb 2015, 01:38
Who help moving this topic to "OS***"
|
|||
09 Feb 2015, 01:38 |
|
revolution 09 Feb 2015, 01:57
It is already there.
|
|||
09 Feb 2015, 01:57 |
|
l4m2 09 Feb 2015, 03:40
revolution wrote: It is already there. It's just moved here. I made a silly mistake : i want "ptr+4" but i inputed "ptr*8" |
|||
09 Feb 2015, 03:40 |
|
cod3b453 10 Feb 2015, 23:34
bochs can be configured to log its execution trace (see logfile and log options sections) to diagnose the source/location/cause of issues:
e.g. Quote: 00949056556e[CPU0 ] read_virtual_dword_32(): segment limit violation |
|||
10 Feb 2015, 23:34 |
|
l4m2 12 Feb 2015, 02:50
cod3b453 wrote: bochs can be configured to log its execution trace (see logfile and log options sections) to diagnose the source/location/cause of issues: Only a silly wrong... |
|||
12 Feb 2015, 02:50 |
|
< Last Thread | Next Thread > |
Forum Rules:
|
Copyright © 1999-2024, Tomasz Grysztar. Also on GitHub, YouTube.
Website powered by rwasa.