e65d4a4906c3529bde5d37a432316030683e6e54
1 /* This file is used to test the 'catch syscall' feature on GDB.
3 Please, if you are going to edit this file DO NOT change the syscalls
4 being called (nor the order of them). If you really must do this, then
5 take a look at catch-syscall.exp and modify there too.
7 Written by Sergio Durigan Junior <sergiodj@linux.vnet.ibm.com>
11 #include <sys/syscall.h>
16 /* These are the syscalls numbers used by the test. */
18 int close_syscall
= SYS_close
;
19 int chroot_syscall
= SYS_chroot
;
20 /* GDB had a bug where it couldn't catch syscall number 0 (PR 16297).
21 In most GNU/Linux architectures, syscall number 0 is
22 restart_syscall, which can't be called from userspace. However,
23 the "read" syscall is zero on x86_64. */
24 int read_syscall
= SYS_read
;
26 int pipe_syscall
= SYS_pipe
;
28 int pipe2_syscall
= SYS_pipe2
;
30 int write_syscall
= SYS_write
;
31 int unknown_syscall
= 123456789;
32 int exit_group_syscall
= SYS_exit_group
;
41 /* A close() with a wrong argument. We are only
42 interested in the syscall. */
49 write (fd
[1], buf1
, sizeof (buf1
));
50 read (fd
[0], buf2
, sizeof (buf2
));
52 /* Test vfork-event interactions. Child exits immediately.
53 (Plain fork won't work on no-mmu kernel configurations.) */
57 /* Trigger an intentional ENOSYS. */
58 syscall (unknown_syscall
);
60 /* The last syscall. Do not change this. */