similar to: Finding instrumented code

Hi all, I am installing a zone onto two different V445s running S10U4 and the zones are taking hours to install (about 1000 packages), that is, the problem is identical on both systems. A bit of trussing and dtracing has shown that the pkginstalls being run by the zoneadm install are making door_call calls to nscd that are taking very long, so far observed to be 5 to 40 seconds, but always in

Is it possible to use DTrace to display the number of arguments and their types for userland or kernel functions that are not explicitly instrumented or documented by their authors? We''re talking about functions provided by Veritas VxVM/VxFS and the like, and for example, we might want to try tracing I/Os from App => VxFS => VxVM => ssd driver to see where I/Os get aggregated or

I am doing some testing on the adjtime syscall, and I want to dump out the value of the kernel variable "timedelta", and I am failing at it. Some of my attempts got "Module is no longer loaded" and some got "Symbol table entry is not a data object" I found some info that dtrace can print out kernel global variable, so what am I missing here? -- blu "Remember

Can i use dtrace to anlayze my core files ? -- This message posted from opensolaris.org

hi, I''m using the PID provider to trace a 32-bit app, prtdiag. I''m trying to print the value of "propname" (arg1) in the following func: int picl_get_propval_by_name(picl_nodehdl_t nodeh, const char *propname, void *valbuf, size_t nbytes) ... i''ve tried many versions, but this is a representative one: 53 this string propname; 54 55

Hello, everyone I am a newbie of DTrace and OpenSolaris. Just wondering is it possible to trace every memory read/write of a specific process given the pid? Basically speaking, I want to record the virtual addresses being accessed by the process, using which I will try to do some online analysis. If DTrace does not support this type of instrumentation, will other tools in OpenSolaris help me

I have a SunRay server that I am looking at to determine some sizing requirements in my department. The machine has 16G of ram and 10G of swap. Currently, I have about 4G of swap used. I am wondering if dtrace/mdb can be used to find out what lwp/processes have been swapped out? Any hints? This message posted from opensolaris.org

Howdy, I am attempting to isolate the location of a memory leak in a 4GL program, and have hit a bit of a snag. When I LD_PRELOAD libumem and run the application server, "::findleaks -fdv" reports numerous leaks: CACHE LEAKED BUFCTL CALLER 0000000100b49068 15 0000000100ef2d50 fdcon+0x6c4 0000000100b50028 1 0000000100b72ac0 fdcon+0x6c4 0000000100b49068

Hi, This is regarding Dtrace usability for memory leak detection. We have real-time application written C++ which runs on Solaris 10 having a problem that''s the my application grows in size from 130 Mb to 450Mb in around 15 days. So there is two possibilities with the application growth of memory due to Size growth of Dictionary Objects (Like Maps) and Memory Leak.

I have found that pid provider can not create memcpy:return probe for 64bit process on snv_110. For example, the pid is 10603, I will have following output for dtrace command: #dtrace -n pid10603:libc.so.1:memcpy:return dtrace: invalid probe specifier pid10603:libc.so.1:memcpy:return: probe description pid10603:libc.so.1:memcpy:return does not match any probes This just

Hi , I have c++ server application in solaries 10 . Day by day memory usage is growing i try to find memory leaks with MDB and DTRACE and no leaks found. how can we find reason for growing memory , can we know which memory sigment is cause for growing memory usage Thanks in Advance. Rao -- This message posted from opensolaris.org

G''Day Folks, I''ve finally typed up my classic DTrace demo, which I use to introduce people to DTrace (I delivered this at SOSUG#1), http://www.brendangregg.com/DTrace/dtracevstruss.html Here I create a fault and show the difficulty in analysing it using previous tools. Then I compare the impact of analysing the problem using both DTrace and truss. DTrace wins (a lot!).

Tracers, Good news! The Solaris Dynamic Tracing Guide has entered the participation age at last and has been converted into wiki format. The new and shiny guide can be found at: http://wikis.sun.com/display/DTrace/Documentation The guide has fallen behind with developments in DTrace since it was first released and needs some revising and some bug fixing as well. However, now that it''s

Hi i''m trying to write my first dtrace script apparently i bit off a bit more than i can chew, i want to track io over sockets, i found your socketsize.d that gave me how to track writes, but i''m at a loss how to track reads, frankly i don''t see how your write tracker works because it uses a probe in a function that only takes two arguments but you grab size of write

I would like to know how to get access to errno when using pid provider to probe calls to libc functions like fopen(). The built-in errno appears to be only for system calls. What I''d like to be able to do is investigate where in an application I''m encountering EMFILE and what the stack looks like at the time. This message posted from opensolaris.org

Bryan, I''m trying to use a Dtrace script with a modest size global variable and hit a problem. Looking for a solution, I turn to the docs and notice that option "dynvarsize" appears just once in the docs, and it refers you to Chapter 3, where there is no mention. It doesn''t help me anyhow. I have: #!/usr/sbin/dtrace -qws #pragma D option dynvarsize=2000000

I''m trying to do some userspace tracing on a server-process with the pid provider. My problem is, that the only probes the pid-provider lists for the server-process (to which I attach dtrace with "-p nnnn") are coming from "ld.so.1". There''s not a single one from my modules. If I''m specifying "a.out" (or any of our shared-objects) as the

Boy am I a dummy. I want to simply dump out unfreed allocations when I terminate the script. What''s the secret sauce? #!/usr/sbin/dtrace -s pid$1::MyAlloc:return { bufs[arg1] = walltimestamp; } pid$1::MyFree:entry /bufs[arg0]/ { bufs[arg0] = 0; } This message posted from opensolaris.org

A complex data structure stored in the shared-memory. Couple of processes attach to the shared-memory... Some of them spawn child procs... Two processes have change notification mechanism encoded... Basically the producer timestamps and the consumer compares the timestamp against it''s snapshot, if they differ then does use a semaphore to lock and gather critical data and replaces the

Can someone, more learned in the ways of dtrace point me at what to look at to help understand why the kernel on one machine is using tons of memory, while another machine doing the same task/same user load is not. swapinfo for the "afflicted" machine shows RAM _______Total 16384 Mb RAM Unusable 73 Mb RAM Kernel 9226 Mb RAM Locked 2 Mb RAM Used