Hacker News Reader

Curious if truss , which was used, or Dtrace would give you the syscalls in a nicer format for this application?

DTrace allows a bunch of nicer filtering (for example by process name, or by function in call stack), but in this case truss was just a no-brainer. I'm not as comfortable with DTrace yet as I'd like to be!

The truss tool has been around for about 30 years, so nothing wrong with sticking with the classics!

Implementation-wise, didn't Solaris adopt dtruss (dtrace-based truss) as truss at some point (and thus Illumos)?

yes, truss has been based on / implemented in terms of dtrace since Solaris 10.

(dtrace userland is a library; you can, if you so choose, write your own tooling there. The command is "just a wrapper", a lot of similarities to bpftrace on Linux)

truss(1) is not DTrace-based. It continues to be implemented in terms of the process control and instrumentation facilities provided by the proc(5) file system, as it has been for a long time.

you're right ... "rusty" memory there. You made me check the sources ... it uses libproc but not libdtrace.

(can I be forgiven since I haven't really touched anything Solaris-ish for near 15 years ?)

Reply on news.ycombinator.com