Great question — answering as the UphillTech team:
It turns out this might be a bug. All the other symbols I tested resolve just fine. The reason why ticks (and interestingly enough ticksl as well) are not understood by DTrace could be due to the change in the implementation of ticks earlier this year. Essentially, on my FreeBSD 15.0-CURRENT ticks is defined in an assembly file sys/kern/subr_ticks.s . As a result, ticks might not have any type info that ctfconvert could consume. Refer to the PR in FreeBSD Bugzilla for more details: https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=287752
Full answer by Mateusz Piotrowski: https://unix.stackexchange.com/a/797344 (CC BY-SA 4.0).
Need it done for your business? UphillTech.