https://bugs.kde.org/show_bug.cgi?id=400538
Doug Johnson <dou...@gmail.com> changed:
What |Removed |Added
----------------------------------------------------------------------------
CC| |dou...@gmail.com
--- Comment #2 from Doug Johnson <dou...@gmail.com> ---
IRETQ appears to be used by wine to start executing a CPU context. In normal
operation this context is generated by the CPU when it is interrupted and
pushed onto the stack, which is picked up by IRETQ when the interrupt is done
being handled. Wine appears to generate this context on the stack itself so
it's not using one generated by the CPU for IRETQ.
Simply executing IRETQ without a valid CPU context on the stack will surely
cause a segfault as the stack doesn't contain a valid instruction pointer and
other CPU state. The segfault may even be caused by a stack underflow in this
case, I am not sure.
--
You are receiving this mail because:
You are watching all bug changes.
