Support x86_64

Question

Support x86_64

mingc00 opened this issue 11 years ago · 12 comments

OS: Ubuntu 12.04.3 LTS
gcc version 4.6.3 (Ubuntu/Linaro 4.6.3-1ubuntu5)

test.c

#include<stdio.h>
int main()
{
    printf("hello world\n");
    return 0;
}

Compile and run

$ gcc test.c -static
$ sudo ./taker ./a.out

I got the message:

Calling   SYS_oldolduname   (id:59  )
Calling   SYS_dup2          (id:63  )
./taker: forbidden operation

fanzeyi commented 11 years ago

@lx75249

Answer 1 · 2013-09-04T05:48:32.000Z

Confirmed this bug.

I tried to allow "dup2" and I have another error message saying that "chdir" is forbidden, but obviously this test sample does not call chdir or anything like that.

Looks like these "forbidden" system calls are in the parent process?

Answer 2 · 2013-09-04T13:34:20.000Z

无法重现.. 我换个环境再试试

Answer 3 · 2013-09-04T13:35:20.000Z

Here: Archlinux x86_64

Something related to 64 bits?

2013/9/4 LX notifications@github.com

无法重现.. 我换个环境再试试

—
Reply to this email directly or view it on GitHubhttps://github.com//issues/5#issuecomment-23789097
.

Hexcles Ma

My Blog: http://robotshell.org/

Answer 4 · 2013-09-04T13:59:59.000Z

system call id in x86_64 is different from that in x86...
an `autoconf' requiring system source code may be available... (or another ugly white list)

Answer 5 · 2013-09-04T14:01:04.000Z

God damn.

2013/9/4 LX notifications@github.com

system call id in x86_64 is different from that in x86...
an `autoconf' requiring system source code may be available... (or another
ugly white list)

—
Reply to this email directly or view it on GitHubhttps://github.com//issues/5#issuecomment-23790975
.

Hexcles Ma

My Blog: http://robotshell.org/

Answer 6 · 2013-09-04T14:09:19.000Z

ok... I find all system call numbers in asm/unistd_xx.h .. an autoconf will be delivered soon.. say good-bye to that brute list

Answer 7 · 2013-09-04T14:09:51.000Z

Doing some search and I got this: strace has a system call table for different arch in its source:

Any help?

Answer 8 · 2018-08-12T13:32:33.000Z

This can be fixed by just updating that list to x64 version. I have succeeded. Thank you for all this work

Answer 9 · 2020-09-01T11:23:13.000Z

I met the same problem，what is the final solution?

Answer 10 · 2020-09-04T21:50:39.000Z

Nothing. The code doesn't work in x86_64; a new syscall list is needed. PRs are welcomed.

Answer 11 · 2020-09-06T00:36:06.000Z

OK,I solved it by remake qaq