search for: mcilree

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

I''m trying to time a function within Firefoxwith a pid$target probe [2]. e.g dtrace -Zqw -x dynvarsize=64m -x evaltime=preinit -p 13954 -s menu- construct.d -s sigcont.d elapsed: 12.7942481ms cpu : 7.7911194ms count : 40 times I''m also measuring Firefox startup time by running it arguments like this: ... file:///Users/joelr/work/mozilla/startup/startup.html#`python

I was looking at mod_trace (http://prefetch.net/projects/apache_modtrace/index.html ) and playing with getting it to compile on OS X. When building for x86_64 with -arch x86_64 we get bad instructions generated: gcc -o foo -arch x86_64 foo.c /var/folders/rV/rV1x2DafFr0R6tGG+1bbk++++TM/-Tmp-//ccnykQ1o.s:11:bad register name `%%esi)'' Using gcc -S I can definitely see we are not

I''ve found what I think is a deadlock in the dtrace fork code. My only Solaris test machine is a single cpu box, where I have been unable to reproduce in the field so far. I''ve been able to reproduce on other platforms. Here is the scenario. You''ve got a target process, which has static probes. It is calling fork(), which causes it to end up at line 330 in fork.c:

How do I query an application to see if it supports any USDT probe points?

On 12/24/06, James McIlree <jmcilree at apple.com> wrote: > > I''ve been reading still more code :-). > > I notice in fasttrap_disable_callbacks(), there is this snippet of > code: > > for (cur = cpu->cpu_next_onln; cur != cpu; >...

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 USDT probes, but I am at a loss on how to

I cannot seem to probe any of the Python interpreter''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

Hi Folks, I''m trying to get to grips with dapptrace, running it on my Mac. Everything seems pretty straightforward, except for - of course - what I''m trying to do. I want to focus in on my code but I can''t seem to be able to output just the functions I want, i.e. user functions. The -U option gives everything. Too much of course. Leaving that blank means the

Hi, Chris (cc) and I try to get the SGE master monitor work with Apple Leopard dtrace. Unfortunately we are stuck with the error msg below. Anyone having an idea what could be the cause? What I can rule out as cause is function inlining for the reasons explained below. Background information on SGE master monitor implementation is under http://wiki.gridengine.info/wiki/index.php/Dtrace

Hi, I was going through the implementation of the fasttrap provider. I found that when displaced execution happens (ie., when the instruction traced is being executed out of the scratch space) if an asynchrnous signal comes we need to defer the delivery. Can somebody explain why this is necessary and how is it implemented? Thanks in advance Saravanan S -------------- next part -------------- An

Tracing Fans, I know it''s been a long time in coming but the CPU Performance Counter (CPC) provider is almost here! The code is currently in for review and a proposed architecture document is attached here for review. Any and all feedback/questions on the proposed implementation is welcome. Thanks. Jon. -------------- next part -------------- An embedded and charset-unspecified text