OSDev.org

Posted: **Tue Jun 02, 2020 3:36 am**

I am on my way to try set up and test idt... so far so good, using bochs, I was able to debug the instructions...
but what I discovered is that (see code below) right after I turned on interrupt (sti), the stack value just changed
dramatically from previous instructions, what happened????

Code: Select all

call isr_handler

pop %ebx
mov %bx, %ds
mov %bx, %es
mov %bx, %fs
mov %bx, %gs
mov %bx, %ss

popa
add 8, %esp
sti
iret

Posted: **Tue Jun 02, 2020 4:18 am**

It looks like you're copying buggy code from a tutorial.

Also, in AT&T syntax, immediate values have a $ prefix.

Posted: **Tue Jun 02, 2020 1:06 pm**

Yeah you are basically adding whatever is at address 8 to %esp. That's not going to work.

Posted: **Tue Jun 02, 2020 8:10 pm**

the dollar sign was there it was $8, i thought about again,and realized that maybe some interrupt signals were causing these...

OSDev.org

stack value changes inside isr_common_stub after sti

stack value changes inside isr_common_stub after sti

Re: stack value changes inside isr_common_stub after sti

Re: stack value changes inside isr_common_stub after sti

Re: stack value changes inside isr_common_stub after sti