DTracers,
Do you know how to fix the failure in the last command ?
TIA,
Bhaskar
# dtrace -A -n ''BEGIN {trace(`kmem_flags); exit(0); }''
dtrace: saved anonymous enabling in /kernel/drv/dtrace.conf
dtrace: added forceload directives to /etc/system
dtrace: run update_drv(1M) or reboot to enable changes
# dtrace -n ''BEGIN {trace(cl_orb`__1cIorb_confMcurrent_node_.ndid);
exit(0);}''
dtrace: description ''BEGIN '' matched 1 probe
CPU ID FUNCTION:NAME
0 1 :BEGIN 1
# dtrace -A
dtrace: cleaned up old anonymous enabling in /kernel/drv/dtrace.conf
dtrace: cleaned up forceload directives in /etc/system
# dtrace -A -n ''BEGIN {trace(cl_orb`__1cIorb_confMcurrent_node_.ndid);
exit(0);}''
dtrace: invalid probe specifier BEGIN
{trace(cl_orb`__1cIorb_confMcurrent_node_.ndid); exit(0);}: relocation
remains against loadable kernel symbol
cl_orb`__1cIorb_confMcurrent_node_ (offset 0x1)
> DTracers, > > Do you know how to fix the failure in the last command ? > > > # dtrace -A -n ''BEGIN {trace(cl_orb`__1cIorb_confMcurrent_node_.ndid); > exit(0);}'' > dtrace: invalid probe specifier BEGIN > {trace(cl_orb`__1cIorb_confMcurrent_node_.ndid); exit(0);}: relocation > remains against loadable kernel symbol > cl_orb`__1cIorb_confMcurrent_node_ (offset 0x1)This does not seem possible as currently there is no runtime kernel symbol relocation support in the dtrace (7D). More specifically, dof sections of type DOF_SECT_KRELHDR needs to be handled for this to work, imo. Thanks Bhaskar