search for: pr_fname

Hi I have a process which reads a socket using recvfrom. After sometime, for no apparent reason, recvfrom exits with an EINTR causing the sender to barf too. Basically the socket on which these processes were communicating no longer exists. On writing a dtrace, I could determine that a signal was received at that socket causing the EINTR. I do not know of way to see who sent the signal (which

...gt;preempt/ { self->preempt = 0; } sched:::off-cpu /self->preempt/ { /* * If we were told to preempt ourselves, see who we ended up giving * the CPU to. */ @[stringof(args[1]->pr_fname), args[0]->pr_pri, execname, curlwpsinfo->pr_pri] = count(); self->preempt = 0; } END { printf("%30s %3s %30s %3s %5s\n", "PREEMPTOR", "PRI","||","PREEMPTED...

...process and to what extent are affected by CPU caps: #!/usr/sbin/dtrace -s #pragma D option quiet sched:::cpucaps-sleep { sleep[args[1]->pr_pid] = timestamp; } sched:::cpucaps-wakeup /sleep[args[1]->pr_pid]/ { this->delta = timestamp - sleep[args[1]->pr_pid]; @sleeps[args[1]->pr_fname] = sum(this->delta); @total[args[1]->pr_fname] = sum(this->delta); } sched:::on-cpu /sleep[curpsinfo->pr_pid]/ { oncpu[curpsinfo->pr_pid] = timestamp; } sched:::off-cpu /oncpu[curpsinfo->pr_pid]/ { this->delta = timestamp - oncpu[curpsinfo->pr_pid]; @cpu[curpsinfo->...

Hi All, One of the customer is seeing the following error messages. He is using a S10U1 system with all latest patches. Dtrace script is attached. I am not seeing these error messages on S10U2 system. What could be the problem? Thanks, Gangadhar. ------------------------------------------------------------------------ rroberto at njengsunu60-2:~$ dtrace -AFs /lib/svc/share/kcfd.d dtrace:

I am trying to use dtrace to trace all sscanf calls. I am able to use pid provider for this. But my application forks off children at times to handle requests. Is there a way I can stop the child process immediately after it is started so that I can attach a pid provider to that and trace the scanf calls in it? I have tried using the "create" probe but that did not help.