|
From: Andy D. <and...@gm...> - 2006-02-04 00:38:15
|
My code is doing a long jump to execute a dynamic syscall in an area of memory mapped into the processes address space by a kernel lib for dynamic syscalls. The instruction for this long jump (see below) appears to not be handled by valgrind 3.1.0. unhandled instruction bytes: 0xEA 0xCD 0x0 0xFF Can anyone confirm that this instruction is not handled? Also, will it be handled in a future release? thanks -andy |
|
From: Tom H. <to...@co...> - 2006-02-07 17:08:46
|
In message <f7f...@ma...>
Andy Davis <and...@gm...> wrote:
> My code is doing a long jump to execute a dynamic syscall in an area of
> memory mapped into the processes address space by a kernel lib for dynamic
> syscalls. The instruction for this long jump (see below) appears to not be
> handled by valgrind 3.1.0.
>
> unhandled instruction bytes: 0xEA 0xCD 0x0 0xFF
>
> Can anyone confirm that this instruction is not handled? Also, will it be
> handled in a future release?
Well clearly it isn't handled or you wouldn't get that error. It is
a far JMP instruction which is a pretty weird thing to see with a
modern operating system outside the kernel.
Why are you using that instruction? Are you trying to switch to a
different code segment? or is the target a call gate or task gate?
Either way I suspect it will be rather hard to support this.
What is a "dynamic syscall" anyway? What is a kernel lib come to that?
Tom
--
Tom Hughes (to...@co...)
http://www.compton.nu/
|