Real Scottish craftspeople enjoy having amazing tooling. They even know how to use a debugger!
Or you have the free time to be a loudmouth online and mouth off about how tech's x y and/or z are dumb and how a shitty bash script is more than enough.
Thankfully I think now Linux has some really great tooling now. But very few people have calls of duty where they are called to do super serious work. Mostly the job calls for pretty simple shit. Make the dumb app go. Throw more servers at the problem someday. The tension is real. It's unfortunate that the cutting edge is so spread out, is so far in advance of the main body of devs.
Other OSes have those too, but they're harder to use and the interfaces aren't as good.
I think it should work if you run `bputil -c`? Didn't try it though.
The idea of dtrace is that you can do that, yes, but to that, you need to be authorized, and the things you can do are (supposed to be) limited to looking to see what’s happening in the system. You can read arguments, but can’t, for example, change the arguments of a system call or disable authorization checks on system calls.
(Or rather, the exception requires restarting the machine to turn the security off.)
Where are the performace tools that wrap those capabilities? IPT has Magic Trace what is the equivalent tool for ARM?
Segger trace[3].
Lauterbach trace[4].
TI Code Composer trace[5].
[1] https://www.ghs.com/video/debug_in_minutes.html
[2] https://ghs.com/products/MULTI_IDE.html
[3] https://youtu.be/sT7N580EI-M?si=53S_DQ5E4IN8AXqM
[4] https://www2.lauterbach.com/pdf/trace_tutorial.pdf
[5] https://software-dl.ti.com/ccs/esd/documents/users_guide_ccs...
Intel has supported such capability via Intel Processor Trace (PT) since at least 2014 [1]. Here is a full trace recorder built by Jane Street feeding into standard program trace visualizers [2].
ARM has supported such capability via the standard CoreSight Program Trace Macrocell (PTM)[3]/Embedded Trace Macrocell (ETM)[4] since at least 2000.
If you pair it with standard data trace, which is less commonly available, then you have the prerequisites for a hardware trace time travel debugger as originally seen in the early 2000s [5]
You can get similar performance/function tracing entirely in software via software-instrumented instruction trace and similar debugging information (though less granular performance information) via record-replay time travel debugger recordings.
[1] https://www.intel.com/content/www/us/en/support/articles/000...
[2] https://blog.janestreet.com/magic-trace/
[3] https://developer.arm.com/documentation/ihi0035/b/Program-Fl...
[4] https://developer.arm.com/documentation/ddi0158/d
[5] https://jakob.engbloms.se/archives/1564