the timeline now draws a curve from the start of each process to its parent process. I added some logic to detect when one process reads a file created by another process, and draws a green line from the last write to the first read to visualize that dependency. Clicking on a process reveals more information about it, including the full command that launched the process, and a list of files it read from and wrote to. I have a filter list to hide common system paths, because theres so many that they drown out the relevant paths. Still trying to figure out what other useful information I can extract, and how best to display it. I've seen that even simple projects tend to have a lot of temporary files that are created and destroyed within one build process, so I'm wondering if I should have a timeline for files too. Not sure if that would give any actionable information though. &wtf

My project can now draw a timeline for make and all the child processes it launches. In this video it's profiling the build of an open source rust project. My program collects syscall/process/timing data in realtime, so in the video you see the timeline scaling to make room for more samples. Above the timeline, I have a list of all the executables used over the course of the build. &wtf

After the first day I have a program that logs all the syscalls of a process and its children. Unlike some other projects here, I'm trying to understand the aggregate behavior of a system (processes communicating and launching each other) rather than the atomic parts (syscalls). So now that I have this stream of juicy data, I want to start extracting some useful insights: what files does each process read and write? What are the dependencies between processes? how long does each process take and what's the bottleneck? The screenshot shows some syscalls from make running ls, with the syscalls of ls indented. &wtf