Re: Undefined SysCall

"Scott J. McCaughrin" <sjmccaug@xxxxxxxxxxxxxxx> writes:

I have a RedHat Linux V Enterprise box with GNU 4.1: while inspecting
the glib, I found that: pthreadlib.a contains a `pthread_create.o'
with the lines:

mov eax,0x137 ;set EAX = 311 (decimal)
int 0x80 ;syscall with undefined code

My x86_64 box only has syscall numbers up to 0x117 (279 decimal),

On Fedora Core 6 (kernel 2.6.19), /usr/include/asm-i386/unistd.h:
....
#define __NR_set_robust_list 311
#define __NR_get_robust_list 312
#define __NR_splice 313
#define __NR_sync_file_range 314
#define __NR_tee 315
#define __NR_vmsplice 316
#define __NR_move_pages 317
#define __NR_getcpu 318
#define __NR_epoll_pwait 319

#endif /* _ASM_I386_UNISTD_H_ */

It is a "standard" glibc technique to issue e.g.
syscall(__NR_set_robust_list), and fall back to other mechanism if
it returns ENOSYS.

Cheers,
--
In order to understand recursion you must first understand recursion.
Remove /-nsp/ for email.
.

Relevant Pages

  • Undefined SysCall
    ... the glib, I found that: ... int 0x80;syscall with undefined code ... My x86_64 box only has syscall numbers up to 0x117, ...
    (comp.os.linux.development.system)
  • MIPS Recursion Help
    ... we're stuck on how to do it using recursion. ... beq $t3, $zero, endLen ...
    (comp.programming)
  • Re: Undefined SysCall
    ... the glib, I found that: ... int 0x80;syscall with undefined code ...
    (comp.os.linux.development.system)
  • Re: How to check number of file handles used by process ???
    ... Jarek writes: ... I don't believe any such syscall exist. ... If /proc is mounted and you are not looking for a portable solution, ... In order to understand recursion you must first understand recursion. ...
    (comp.os.linux.development.apps)
  • [patch] PPC debug setcontext syscall implementation.
    ... A syscall has been reserved for a debug setcontext for PPC, ... Add a debugging interface for PowerPC that allows signal handlers (or any ... volatile int called2 = 0; ...
    (Linux-Kernel)