recentpopularlog in


« earlier   
Using C to inspect Linux syscalls | OpsTips
A deep dive into how to make use of ptrace to inspect syscalls made by a tracee while they occur.
c  strace  5* 
26 days ago by ianweatherhogg
Dynamic shared library strace
Strace of a dynamic shared library program loading procedure
strace  syscall 
5 weeks ago by xxr3376
Remote Code Execution in Alpine Linux
tl;dr I found several bugs in apk, the default package manager for Alpine Linux. Alpine is a really lightweight distro that is very commonly used with Docker...
alpine  strace 
5 weeks ago by ianweatherhogg
Debugging Stuck Ruby Processes—What to do Before You Kill -9
You can also use other tracing tools to examine the behavior of the looping process. On Linux, strace -p <pid> allows you to view the system calls being made by the process. If you’re on an OS that has dtrace available, you can use dtruss -p <PID> instead to get a similar output.

On Linux:
# strace -p <pid>

On Mac:
# dtruss -p <pid>

gdb -p <pid>
(gdb) t a a bt
(gdb) call (void)rb_backtrace()
strace  osx  dtruss  ruby  debug  debugging 
8 weeks ago by hellsten
Intercepting and Emulating Linux System Calls with Ptrace « null program
The ptrace(2) (“process trace”) system call is usually associated with debugging. It’s the primary mechanism through which native debuggers monitor debuggees on unix-like systems. It’s also the usual approach for implementing strace — system call trace. With Ptrace, tracers can pause tracees, inspect and set registers and memory, monitor system calls, or even intercept system calls.
ptrace  strace  debugging  linux 
june 2018 by euler

Copy this bookmark:

to read