search for: dtrace_systrace_syscall

Referring to the DTrace manual: "Module If this probe corresponds to a specific program location, the name of the module in which the probe is located. This name is either the name of a kernel module or the name of a user library. Function If this probe corresponds to a specific program location, the name of the program function in which the probe is located." and then ...

...bc.so.1`write+0x75[/u][/b] a.out`main+0x43 a.out`_start+0x7a syscall::write:entry unix`sys_sysenter+0x101 [b] libc.so.1`_write+0x15 a.out`main+0x43[/b] a.out`_start+0x7a fbt:genunix:write:entry genunix`dtrace_systrace_syscall+0xb9 unix`sys_sysenter+0x101 libc.so.1`_write+0x15 [u]a.out`main+0x43[/u] a.out`_start+0x7a pid17632:libc.so.1:write:return libc.so.1`write+0x90 a.out`_start+0x7a when syscall probe fires ,why does the stack infor...

Now at 36 hours since zdb process start and: PID USERNAME SIZE RSS STATE PRI NICE TIME CPU PROCESS/NLWP 827 root 4936M 4931M sleep 59 0 0:50:47 0.2% zdb/209 Idling at 0.2% processor for nearly the past 24 hours... feels very stuck. Thoughts on how to determine where and why? -- This message posted from opensolaris.org