search for: ustack

I have a test program which has a call sequence of a(), b(), c(), d(). When I place a pid return probe on d(), I get a ustack that looks like this: a.out`d+0x19 a.out`b+0xd a.out`a+0xd a.out`main+0x3c a.out`_start+0x7a The c() method appears to be missing. I did some poking around and noticed that pid return probes fire after the instruction b...

Hello, The Hotspot JVM Runtime group would like to put forth a project proposal to improve the capabilities of DTrace''s ustack()/jstack() actions to better handle non-standard user stack frames. This email will describe the background, the problem, and our proposed solution. We''re interested in getting a sponsor for this work to help us with the process of getting the code into the solaris codebase, and we...

I am trying to integrate John Levon''s ustack() helper for Python into the upstream Python sources. The method for doing this on Solaris is to compile the phelper.d script containing the helper into an object file using "dtrace -G". dtrace on OS X does not have "dtrace -G", just "dtrace -h". This works fine for...

I have been doing some profiling using the profile provider. I have a command that runs more slowly on the T1000 than it does on prior systems and I am trying to find out why. Using the profile provider at 1000 hz, and aggregating on the ustack output, I find that the same function appears at the top of the stack on both platforms, but on each there are specific instruction locations within the function that appear most often and these are different on the two platforms. They are consistent on a platform. That is when I re-run the tes...

As of patch 32953 dtrace support is in bleadperl (5.11.0). The probes are based on Alan Burlinson''s original blog post on the subject: http://blogs.sun.com/alanbur/date/20050909 By guarding the probes with PERL_SUB_*_ENABLED the performance hit is unmeasurable. All the necessary bits already existed in the wild. I just assembled them and made the necessary changes to

...ided to change the free:entry probe from: pid24169::free:entry / sz[arg0] / { printf("Freeing %p (size %d)\n", arg0, sz[arg0]); sz[arg0] = 0; } to: pid24169::free:entry / ! sz[arg0] / { printf("[ * ] A bad function is Freeing memory at address %p\n",arg0); ustack(); } When I created a test program [1] and attempted to run the new script, I got the following output: $ dtrace -q -s foo.d -c ./fluffy fluff: 20a30 [ * ] A bad function is Freeing memory at address ff3f1298n ld.so.1`free ld.so.1`setup+0x13ac ld.so....

Hi all, I am trying to write a D script which would print ustack() for every program in the system receiving SIGSEGV. All the stacks printed in trap()/sigtoproc() context do not have meaningful symbols. The following solves the problem to some degree but I''d much rather have a self-contained D script. dtrace -w -n ''fbt:genunix:sigtoproc:en...

Hi Ryan, > Does anyone happen to know why the ustack() doesn''t show lex, > yak, main > and _start? A quick look with the source browser seems to indicate that _rt_boot is code executed very early in the lifetime of your process by ld.so.1. What seems to be happening is that ld.so.1 has allocated some memory before DTrace got control...

...ngled enclosing function name for the probes Function name. Working around this can be a pain. You need to wrap your usdt probes in extern C functions and call these. Could we have an option to control the Function name for usdt probes, not just the Name in the probe definition file? Accessing ustack entries as strings to aggregate on: Also whilst controlling the Function name we''d still like to be able to access the name of the C++ calling function of our wrapped probe. Is there any way for us to do this? I can use ustack(2) to print out 2 levels of the stack, but what I''d...

...the total time for which each thread in my application sleeps, blocked on a semaphore, i.e., as a result of sem_wait() call. In order to measure this, I wrote a script with sched:::sleep and sched:wakeup probes enabled, as shown below: sched:::sleep /execname == "myexecname"/ { ustack(); bedtime[curlwpsinfo->pr_addr,curlwpsinfo->pr_stype] = walltimestamp; } sched:::wakeup /bedtime[args[0]->pr_addr,args[0]->pr_stype]/ { @sleeptime[execname,args[0]->pr_lwpid,args[0]->pr_addr,args[0]->pr_stype] = sum(walltimestamp - bedtime[args[0]->pr_addr,ar...

...ignal-send /args[1]->pr_pid == $target/ { last_signal = args[2]; last_signal_sender_pid = pid; last_signal_sender_name = execname; } proc:::exit /pid == $target && args[0] == CLD_EXITED/ { printf( "%Y normal exit.", walltimestamp ); ustack(); } proc:::exit /pid == $target && args[0] == CLD_KILLED/ { printf( "%Y exited by signal. signal=%d, sent by=%s (%d)", walltimestamp, last_signal, last_signal_sender_name,...

I''m pleased to pass along news that the Mac OS X DTrace port has been updated in 10.5.3 to fix the issue that caused timer based probes not to fire in the presence of certain untraceable applications. http://blogs.sun.com/ahl/entry/apple_updates_dtrace A big thank you to the folks at Apple for addressing the problem. Adam -- Adam Leventhal, Fishworks

...nts to execute it (thank goodness for inefficiency), I thought I would use arg0 to open and rnrq+0x204 to isolate the program file that contains the problematic code. When I attempt to run the following DTrace to enable the probe at rnrq:204: $ dtrace -p 4243 -n ''pid$target::rnrq:204 { ustack(); }'' dtrace: description ''pid$target::rnrq:204 '' matched 1 probe The probe never fires. Does anyone see anything wrong with what I am doing? Thanks for any insight, - Ryan -- UNIX Administrator http://daemons.net/~matty

...ter''s C functions on OS X. $ sudo dtrace -n ''pid$target::PyEval_EvalFrameEx:entry'' -c python dtrace: invalid probe specifier pid$target::PyEval_EvalFrameEx:entry: probe description pid59706::PyEval_EvalFrameEx:entry does not match any probes These functions show up in ustack()s, but they do not appear to be available for probing. There do not appear to be any probes in the "a.out" module: $ sudo dtrace -n ''pid$target:a.out::entry'' -c python dtrace: invalid probe specifier pid$target:a.out::entry: probe description pid59714:python::entry...

In Solaris 10 6/06, etc. I used to do things like pid$target::malloc:entry { ustack(); } and got stack traces from my application calling malloc as expected. In Solaris 10 8/07 I only see stack traces from functions inside libc calling a function called lmalloc() but not my malloc calls: ld.so.1`lmalloc ld.so.1`tsort+0xb4 ld.so.1...

Hi: On niagara system, I am trying to resolve the Lock contention which results in low CPU usage. I have probed the Mutex hold event for heavy expensive lock releasing during user land processes test cycle. Any way to further investigate the call below is contributed by system library, user land process or kernel lock. This Mutex Hold: libsyssrv.so`__1cHSWMutexLmutexUnlock6M Thanks This

...stat 305050713 getdirentries 480578501 poll 60233510027 extattr_get_file 63198610831 I decided to poke around a bit since I am a noob and noticed the following errors in my dtrace output: trace -n 'syscall:::return /execname=="smbd"/ {@[ustack)] = count(); }' libc.so.7`__sys_close+0xc libsmbd_base.so`smb_vfs_call_closedir+0x50 libsmbd_base.so`0x800b27a92 libtalloc.so.2`0x8036b205e dtrace: ERROR: open failed: No such file or directory `0x8115768c0 dtrace: ERROR: o...

...ue,strlen(value)); } } //////////////////////////////////////// and the dtrace script (write.d) is: syscall::write:entry, fbt::write:entry, pid$1::write:entry, pid$1::write:return, pid$1::_write:entry /pid==$1/ { printf("%s:%s:%s:%s\n",probeprov,probemod,probefunc,probename); stack(100); ustack(100); } /////////////////////////////// when runs the script, the result is : pid17632:libc.so.1:write:entry libc.so.1`write a.out`main+0x43 a.out`_start+0x7a pid17632:libc.so.1:_write:entry [b] libc.so.1`_write [u]libc.so.1`write...

I''m trying to install CiscoWorks 2.5 on Solaris 10 update 1, and after the install when I try to start the daemon, it errors: # /opt/CSCOpx/objects/dmgt/dmgtd.sol ERROR: open file dmgtd failedERROR >>>>>>>>>>>>> open msg catalog failed. NLSPATH incorrect or objects/share/nls/C/dmgtd.cat is missing. # echo $NLSPATH

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