If you app is spinning in userland, you want to try profiling.
profile-1001/{pid == <targetpid>/[EMAIL PROTECTED]()] = count()}
That should give you an idea of what the busiest userland stack look
like. You can then use mdb or the pid provider to zoom in on that
function.
On Tue, Apr 1, 2008 at 6:45 AM, Gautam Gopalakrishnan
<[EMAIL PROTECTED]> wrote:
> > I'm afraid your question is not good enough to give good enough answer
>
> Doh!
>
>
> > Are you talking about userland or kernel?
>
> I am talking about a userland application which does database queries.
> To simplify, let's say main() calls A(). Sometimes A takes too long to
> return, so I want to know what parameters were passed (maybe the query
> is too broad or inefficient). If I run a DTrace script at this point,
> the pid$1::A:entry fbt provider will not be triggered and
> pid$1::A:return will be too late (because the problem does not exist
> anymore). If A() is a small function, then I could put a probe on every
> instruction but in this case it is complex and calls many other functions.
>
>
> > There is another option, called static probes.
>
> I can't recompile the application :( I'm just a support guy.
>
>
> > I hope I answered you question. If not, sorry :)
>
> Thank you, much appreciated.
>
> Regards
>
>
> -Gautam
> _______________________________________________
> dtrace-discuss mailing list
> [email protected]
>
--
Just me,
Wire ...
Blog: <prstat.blogspot.com>
_______________________________________________
dtrace-discuss mailing list
[email protected]
