Searched refs:strace (Results 1 – 7 of 7) sorted by relevance
/linux-3.4.99/Documentation/security/ |
D | Yama.txt | 33 parent to a child process (i.e. direct "gdb EXE" and "strace EXE" still 34 work), or with CAP_SYS_PTRACE (i.e. "gdb --pid=PID", and "strace -p PID"
|
/linux-3.4.99/arch/alpha/kernel/ |
D | entry.S | 303 blbs $3, strace 417 .ent strace 418 strace: label 477 .end strace
|
/linux-3.4.99/arch/m68k/kernel/ |
D | entry_mm.S | 80 movel #-ENOSYS,%sp@(PT_OFF_D0)| needed for strace
|
/linux-3.4.99/Documentation/s390/ |
D | Debugging390.txt | 32 strace 897 strace: 911 strace ping -c 1 127.0.0.1 957 strace passwd 2>&1 | grep open 987 /usr/bin/strace -o/t1 -f /usr/sbin/in.telnetd -h 997 -o is used to tell strace to output to a file in our case t1 in the root directory 1001 of the strace output. 1002 -p<pid> will tell strace to attach to a running process, yup this can be done provided 1004 the reason 2 processes cannot trace or debug the same program is that strace 1023 an strace of both programs under as identical a scenario as you can [all …]
|
/linux-3.4.99/Documentation/ioctl/ |
D | ioctl-number.txt | 47 (2) The 'strace' build procedure automatically finds ioctl numbers 50 (3) 'strace' can decode numbers back into useful names when the
|
/linux-3.4.99/Documentation/virtual/uml/ |
D | UserModeLinux-HOWTO.txt | 2870 Below is an example of using strace as an alternate debugger. 2886 An example of an alternate debugger is strace. You can strace the 2893 sh -c 'echo pid=$$; echo -n hit return; read x; exec strace -p 1 -o strace.out' 2900 o Hit return in the shell, and UML will start running, and strace 2906 host% strace ./linux 2911 That will strace only the main UML thread, the tracing thread, which 2913 tual machine. In contrast, using strace as described above will show
|
/linux-3.4.99/ |
D | CREDITS | 395 D: strace for Linux/Alpha 3268 D: utility hacker: Emacs, NFS server, mount, kmem-ps, UPS debugger, strace, GDB
|