Explore >> Select a destination

You are here

 abstractexpr.com
Limiting which Syscalls to Trace with Strace - Abstract Expression
| | nora.codes
Additional Exercises in Reverse Engineering | Nora Codes
6.2 parsecs away

Travel
| |
| | crocidb.com
Demystifying the #! (shebang): Kernel Adventures - Bruno Croci
14.3 parsecs away

Travel
| | Clarifying the shebang (#!) mechanism: A step-by-step look using strace and kernel code shows how Linux handles script execution directly, revealing the shell isn't involved initially.
| | www.integralist.co.uk
Terminal Debugging Utilities ? Mark McDonnell
10.2 parsecs away

Travel
| | Introduction Prerequisites TCP and HTTP OSI Model Utilities top: check running processes for cpu and memory utilisation ps: see what processes are running strace: monitor interactions between processes lsof: list of open files netstat: monitoring network traffic ifconfig: configure or review your network interfaces iftop: monitors network traffic and displays table of bandwidth usage iptraf: monitoring network traffic (more visual than netstat, not as detailed) tcpdump: network packet sniffer wireshark: ...
| | psychocod3r.wordpress.com
Reverse-Engineering a Linux Process with strace - Psycho Cod3r
20.1 parsecs away

Travel
| The pill you took is part of a trace program. It's designed to disrupt your input/output carrier signals so we can pinpoint your location. And just like that, we can trace signals as they bounce around the Matrix, whether it's the Matrix that simulates Earth in 1999 or the Matrix that generates pretty pictures on...