Saturday, December 12, 2009

Interrupted Before Acronis True Image Assembler: When Writing An Interrupt Handler, How Do You Find Out The Pointer To Where Execution Was Before?

Assembler: When writing an interrupt handler, how do you find out the pointer to where execution was before? - interrupted before acronis true image

It's hard to fit in 110 characters ...
Origins - I write a very simple operation. If an interrupt does not generate a code (or generated code is produced for that matter) as my operating system handles, how do I know if was the execution of code before the break?
This is especially important when you try multitasking operating system - I am the RTC (Real-Time Chip) for change, and my operating system must use to know where he was executed, and save it for when it can be changed back to activate the program again.
If you have any questions, please contact me via e-mail.

5 comments:

MegaBrut... said...

Is stored in all calls of the last address in the real cell. If the process is interrupted, the battery is used to the caller, so you should be able to read it. I had a good book about him, but from the library. : (Maybe you should try Google for more information, that's all I know.

MegaBrut... said...

Is stored in all calls of the last address in the real cell. If the process is interrupted, the battery is used to the caller, so you should be able to read it. I had a good book about him, but from the library. : (Maybe you should try Google for more information, that's all I know.

MegaBrut... said...

Is stored in all calls of the last address in the real cell. If the process is interrupted, the battery is used to the caller, so you should be able to read it. I had a good book about him, but from the library. : (Maybe you should try Google for more information, that's all I know.

Darren D said...

should be somewhere in the stack. Experiment with elements of pop and address should be there. I suppose it could be larger than one byte, it would blow up the air more than one item, and check the underlying addressing mode (big / little endian)

Darren D said...

should be somewhere in the stack. Experiment with elements of pop and address should be there. I suppose it could be larger than one byte, it would blow up the air more than one item, and check the underlying addressing mode (big / little endian)

Post a Comment