Date: Mon, 23 Jun 2025 15:46:55 +0000 From: bugzilla-noreply@freebsd.org To: bugs@FreeBSD.org Subject: [Bug 287752] DTrace error: no symbolic type information is available for kernel`ticks: No type information available for symbol Message-ID: <bug-287752-227@https.bugs.freebsd.org/bugzilla/>
index | next in thread | raw e-mail
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=287752 Bug ID: 287752 Summary: DTrace error: no symbolic type information is available for kernel`ticks: No type information available for symbol Product: Base System Version: 15.0-CURRENT Hardware: Any OS: Any Status: New Severity: Affects Only Me Priority: --- Component: kern Assignee: bugs@FreeBSD.org Reporter: 0mp@FreeBSD.org One of the examples on https://wiki.freebsd.org/DTrace/One-Liners does not work anymore on a recent FreeBSD 15.0-CURRENT. Let's consider this one-liner: dtrace -n 'fbt::tcp_close:entry { @["TCP life span (seconds):"] = quantize((uint32_t)(`ticks - args[0]->t_starttime) / `hz); }' It errors out with: dtrace: invalid probe specifier fbt::tcp_close:entry { @["TCP life span (seconds):"] = quantize((uint32_t)(`ticks - args[0]->t_starttime) / `hz); }: in action list: no symbolic type information is available for kernel`ticks: No type information available for symbol It seems like there is something wrong with `ticks. `hz works just fine. I spoke with markj@ about it and he suggested that it might be related to clock: Add a long ticks variable, ticksl (https://cgit.freebsd.org/src/commit/?id=6b82130e6c9add4a8892ca897df5a0ec04663ea2). -- You are receiving this mail because: You are the assignee for the bug.home | help
Want to link to this message? Use this
URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?bug-287752-227>