On Tue, Jan 08, 2002 at 10:36:08AM +0200, guy keren wrote:
someone once told me of the following wish for a program - we allocate
small buffers that read data (from the network, for example). once we're
acknowledged that we got enough data, we want to pass the entire
stream to a module that
Rafi Gordon wrote:
Hello,
Processes can change their Local Descriptor Table using
modify_ldt() system called.
see man modify_ldt or :
(for x386 look at include/asm-i386/unistd.h:
#define __NR_modify_ldt 123)
However, usually there is no need to manipulate the LDT
with this system call.
Hello,
Processes can change their Local Descriptor Table using
modify_ldt() system called.
see man modify_ldt or :
(for x386 look at include/asm-i386/unistd.h:
#define __NR_modify_ldt 123)
However, usually there is no need to manipulate the LDT
with this system call.
I saw in wine a
On Tue, Dec 27, 2005 at 02:46:59PM +0200, Rafi Gordon wrote:
I was wondering in which occasions is this
system call being invoked: did anybody had encountered (or used himeslf)
a call to modify_ldt() in other apps (emulators maybe ? ).
qemu uses it:
The Linux system call modify_ldt() is used
Muli Ben-Yehuda wrote:
On Tue, Dec 27, 2005 at 02:46:59PM +0200, Rafi Gordon wrote:
I was wondering in which occasions is this
system call being invoked: did anybody had encountered (or used himeslf)
a call to modify_ldt() in other apps (emulators maybe ? ).
qemu uses it:
The Linux
On Tue, Dec 27, 2005 at 04:22:22PM +0200, Shachar Shemesh wrote:
The ultimate upshot of all of the above is that Wine jumps throgh hoops
trying to make sure that the memory image under Linux is the same as the
memory image under Windows for loaded programs. I will not be the least
surprised
On Tue, 27 Dec 2005, Rafi Gordon wrote:
Hello,
Processes can change their Local Descriptor Table using
modify_ldt() system called.
see manmodify_ldt or :
(for x386 look at include/asm-i386/unistd.h:
#define __NR_modify_ldt 123)
However, usually there is no need to manipulate the
