Brilliant thanks. Crucial point about the CPUs. That explains a lot of
what I'm seeing.
Cheers,
Max
On 2 Nov 2009, at 17:49, Jonathan Adams wrote:
On Mon, Nov 02, 2009 at 12:46:45PM +0000, Max wrote:
Hi Folks,
I'm trying to use DTrace to understand some complex code using the
user process probe.
Things are basically not matching up. When I use a variable to track
depth, sometimes it jumps. Similarly, the flow indent seems off.
Remember that data is stored in per-CPU buffers, which are then
printed
out all-at-once. If you have long-running data which can run on
multiple CPUs, you'll need to print out "timestamp", then sort the
output
by that field for everything to line up.
Cheers,
- jonathan
I read another post saying that this is caused by missing return
statements in functions.
http://mail.opensolaris.org/pipermail/dtrace-discuss/2005-June/000011.html
Problem is I'm a bit of a newbie with DTrace so although I get the
general idea of the post, I'm still a bit confused about how to do a
workaround.
Would anyone have any advice on how to resolve this?
Ideally I'm just after a way to reliably trace function entries and
returns.
Any advice would be much appreciated.
Thanks,
Max
_______________________________________________
dtrace-discuss mailing list
dtrace-discuss@opensolaris.org
_______________________________________________
dtrace-discuss mailing list
dtrace-discuss@opensolaris.org
