Displaying 20 results from an estimated 30000 matches similar to: "fbt::cpu_mstate_new:new not found."
2006 Jun 30
2
Qs. on fbt::copystr: probe
Hi all,
I have questions about something I observed just now:
1) on AMD64, S10u1:
# dtrace -n ''fbt::copystr:entry{printf ("%p\n", args[0]);}'' -c /bin/pwd
dtrace: invalid probe specifier fbt::copystr:entry{printf ("%p\n",
args[0]);}: in action list: index 0 is out of range for fbt::copystr:entry
args[ ]
but
# dtrace -n ''fbt::copystr:entry{printf
2007 Jul 11
5
Error trying to count return points in functions.
Whilst trying out some D to get an insight into what is the most
common reason for a given function to return, I have bumped
into an error I don''t understand.
The first take on what I was trying to do was:
# dtrace -n ''fbt:ip:ip_input:return{@home[arg0] = count();}''
and all was well. The next step was:
# dtrace -n
2009 Mar 09
2
FBT Provider
Is there a list anywhere of the DTrace FBT provider calls for each version of Solaris since the Nevada build that hosed the DTrace Toolkit. I have no issue with rewriting what I need, but I am hoping to stave off having to look at all the source code to find everything. I know there is a new provider under development, but I need to be able to program DTrace routines for all the updates in
2006 Jul 07
2
Probe ID changes
OK, I''ve been fritzing around with something I noticed last night,
thinking that I understood what was going on, but now it''s getting
confusing again.
A system that has been running for a couple of months had a hole in the
probe ID list near the end in the middle of the fbt probes. And then a
couple of syscall probes were stuck in the hole. It looked like this:
...
40311
2006 Jun 03
1
man pages for each providers ?
Hey,
Do you guys think that is a good idea to have a manual page for each provider with a complete description of what probes are offered ? Found some already under 7D category:
dtrace dtrace (7d) - DTrace dynamic tracing facility
fasttrap fasttrap (7d) - DTrace user instruction tracing provider
fbt fbt (7d) - DTrace function boundary tracing provider
2005 Jul 15
0
Re: Debugging Linux binaries with Dtrace?
Hi Nils, all,
I tried the ''FBT-trick'' suggested below by Nils and (of course :-) ) it
works and gives me a pile of output. Good enough to show that indeed Linux
application behavior is not totally opaque, good enough to for instance show
that ''system call mapping'' is taking place.
I wonder, is there any documentation available for lxsyscall module ? To
learn
2007 Dec 25
6
what is differenct between syscall::write:entry fbt::write:entry
what is differenct between syscall::write:entry fbt::write:entry
are the two probe fires at the same place.
--
This message posted from opensolaris.org
2007 Aug 21
2
Extremely long creat64 latencies on higly
Thanks Michael.
Here is my (slightly corrected) version of the script, after I''ve done a bit of investment in the dtrace manual (always knew it''s powerful, but it''s more than that...).
While it appears to run, and when I tried lowering the limit I started getting results, I''d appreciate it if you could please explain the actions attached to the last few probes
2005 Oct 26
1
Error message with fbt::copen:entry probe
All,
The attached script is causing the following error message ...
bash-3.00# ./zmon_bug.d
dtrace: error on enabled probe ID 2 (ID 4394: fbt:genunix:copen:entry):
invalid address (0xfd91747f) in predicate at DIF offset 120
dtrace: error on enabled probe ID 2 (ID 4394: fbt:genunix:copen:entry):
invalid address (0xfef81a3f) in predicate at DIF offset 120
Any ideas?
thxs
Joe
--
2006 Jul 10
5
Definition of "anchored" and "unanchored" probes
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 ...
2008 Aug 20
0
anonymous tracing
I''m using DTrace''s anonymous tracing feature to trace through device
drivers at boot time. With Solaris 10 Update 6 B5, I was unable to trace
fbt based calls from the sd attach point. The error messages from the
console are:
NOTICE: enabling probe 0 (fbt::sdattach:entry)
NOTICE: enabling probe 1 (fbt:::)
NOTICE: enabling probe 2 (fbt::sdattach:return)
NOTICE: enabling probe
2006 Oct 31
0
6256581 System got a hang or a panic with dtrace+kmdb
Author: bmc
Repository: /hg/zfs-crypto/gate
Revision: 213bfe03af413cdf71c523fb076aaa65a6306a7e
Log message:
6256581 System got a hang or a panic with dtrace+kmdb
6264573 unanchored dtrace_getpcstack is rather imprecise toward function end
6289517 dtrace doesn''t like fd_intr anymore
6291378 dtrace helpers can interfere with the use of kmdb
6295554 dtrace doesn''t report
2006 Sep 21
1
Dtrace script compilation error.
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:
2007 Dec 29
1
why was some stack information lost.
I wrote a simple c programme and do some dtrace test. the progromme shows below(write.c):
///////////////////////////////
#include<stdio.h>
#include <sys/types.h>
#include <sys/stat.h>
#include <fcntl.h>
char *value="hello,my name is wanjm\n";
void main()
{
int fd;
fd=open("/export/home/wanjm/temp/read.txt",O_RDWR|O_CREAT);
while(1)
{
2006 Sep 13
0
Fwd: Systemtap vs Dtrace web page corrections.
Hi
Here is System tap''s representives response to my comments and mine
back to that list. Since it was on a public mailing list i''m reposting
here, since there is obvious interest.
James Dickens
uadmin.blogspot.com
---------- Forwarded message ----------
From: James Dickens <jamesd.wi at gmail.com>
Date: Sep 13, 2006 1:51 PM
Subject: Re: Systemtap vs Dtrace web page
2007 Mar 10
4
Functions that cannot be traced by FBT under x86
Hi All:
In Solaris Dtrace User Guide, page 218, it says,
"Functions that do not create a stack frame on x86 systems cannot be
instrumented by FBT."
Then what are these functions?
What characteristics do they have?
Regards
TJ
2011 Oct 26
1
Problem running zilstat script on a core install server.
We cannot run the zilstat utility (from
http://www.richardelling.com/Home/scripts-and-programs-1/zilstat) on
an Solaris 10 u9 / x86 installed according SUNWCreq (which is a core
install)
while it works fine on a similar config but installed with all
packages (SUNWCXall)
So we know it works in this environment but it seems we miss an
essential package here. That causes the
dtrace: failed to
2008 Sep 09
1
DTrace and shared memory id
Hello all,
I saw this question about a year back in the archive[1], but with no
final answer.
I would like to trace shmget calls and also get the id of the shared
memory segment.
That script looked like[2], but we dont get the id since arg1 is the
errno value.
How do i access the shm id, i would need this to debug a customer
problem but i don''t have time to learn it the hard
2007 Jun 21
3
Anon tracing error?
Hello,
I''ve done this several times in the past but a co-worker is having problems
getting anonymous tracing to work:
dtrace -A -m su
and we see updated /kernel/drv/dtrace.conf and fbt and dtrace forceloads
added to /etc/system. Upon reboot the following errors occur (note that
we are running snv_66):
{0} ok boot disk
Boot device: /pci at 0/pci at 0/pci at 2/scsi at 0/disk at 0 File
2005 Nov 17
3
Abort due to systemic unresponsiveness
What is causing this error:
dtrace: processing aborted: Abort due to systemic unresponsiveness
It happens to my script which shows all the NFS operations coming
through common_dispatch() on a server.
I wasn''t the one running the test, so I don''t know how long it ran
before it died.
The script uses a couple of static probes and a couple fbt.
Thanks,
jim
-------------- next