Question about which tools to use, bugs, the best way to implement a function, etc should go here. Don't forget to see if your question is answered in the wiki first! When in doubt post here.
mrjbom wrote:I expect a #DB exception to be thrown when writing a new value, but this does not happen.
Well, maybe because that is a dead store. Or maybe the compiler allocates "a" into some register and will only spill it later. For things like that, I have set and read functions in my io.S that work exactly like the in and out functions, but for memory space instead of I/O space:
Then you can force the write to occur with "setl(&a, 123)". And that really should trap with #DB in your case. Of course, this is for 64-bit mode, you would need something like
Oh my God, what a stupid mistake, how could I have made such a mistake, I'm ashamed of such a stupid mistake.
I'm confused about the syntax.
Thank you for noticing.
mrjbom wrote:
Oh my God, what a stupid mistake, how could I have made such a mistake, I'm ashamed of such a stupid mistake.
I'm confused about the syntax.
Thank you for noticing.
If you want a stupid mistake, try the hours I spent debugging a keyboard driver...
mrjbom wrote:
Oh my God, what a stupid mistake, how could I have made such a mistake, I'm ashamed of such a stupid mistake.
I'm confused about the syntax.
Thank you for noticing.
If you want a stupid mistake, try the hours I spent debugging a keyboard driver...
"=" instead of "==".
We've all been there!
Heh, you're right.
Perhaps the same stupid error is the cause of this topic's problem... I still can't solve it(