|
From: yami <ya...@gm...> - 2009-09-28 02:21:29
|
Hi, I tried to run a amd64-linux program on valgrind 3.5.0, but valgrind said modify_ldt syscall is missing. After checking the 3.5.0 source code, I think Valgrind 3.5.0 does not support modify_ldt amd64-linux. Is there a plan to implement it recently? Or how hard is it to support modify_ldt on amd64-linux? If it is not hard, I'll tried to port x86 support to amd64 by myself. However I looked at VEX/pub/libvex_guest_amd64.h, but it seems that VexGuestAMD64State does not have a full support for segmentation registers... Your comments are really appreciated. Thanks! |
|
From: tom f. <tf...@al...> - 2009-09-28 03:51:46
|
yami <ya...@gm...> writes: > I tried to run a amd64-linux program on valgrind 3.5.0, but valgrind > said modify_ldt syscall is missing. After checking the 3.5.0 source > code, I think Valgrind 3.5.0 does not support modify_ldt amd64-linux. http://valgrind.org/docs/manual/dist.readme-missing.html See: "Writing your own syscall wrappers (see below for ioctl wrappers)" -tom |
|
From: Tom H. <to...@co...> - 2009-09-28 07:33:42
|
On 28/09/09 04:54, tom fogal wrote: > yami<ya...@gm...> writes: >> I tried to run a amd64-linux program on valgrind 3.5.0, but valgrind >> said modify_ldt syscall is missing. After checking the 3.5.0 source >> code, I think Valgrind 3.5.0 does not support modify_ldt amd64-linux. > > http://valgrind.org/docs/manual/dist.readme-missing.html > > See: "Writing your own syscall wrappers (see below for ioctl wrappers)" Perfectly good advice for a "normal" system call, but modify_ldt is very much a special case and is not at all simple to implement. Ticket https://bugs.kde.org/show_bug.cgi?id=175985 is already open for this. Using modify_ldt on x86_64 is pretty unusual though so it doesn't look like there has been much headway in fixing it. Tom -- Tom Hughes (to...@co...) http://www.compton.nu/ |