site_archiver@lists.apple.com Delivered-To: darwin-dev@lists.apple.com profile-997 /pid == $target/ { @[ustack()] = count() } /* stop tracing here */ pid$target:XUL:XRE_main:entry { exit(0); } END { trunc(@, 25) } Don't forget to file a bug report about this. Eric Thanks, Joel --- fastest mac firefox! http://wagerlabs.com _______________________________________________ Do not post admin requests to the list. They will be ignored. Darwin-dev mailing list (Darwin-dev@lists.apple.com) Help/Unsubscribe/Update your Subscription: http://lists.apple.com/mailman/options/darwin-dev/site_archiver%40lists.appl... On Aug 24, 2009, at 4:02 PM, Joel Reymont wrote: I get a bunch of memory access errors when trying to run my script, e.g. dtrace: script 'high.d' matched 2 probes dtrace: allowing destructive actions dtrace: error on enabled probe ID 1 (ID 36: profile:::profile-997): invalid address (0xbffff7c8) in action #2 dtrace: error on enabled probe ID 1 (ID 36: profile:::profile-997): invalid address (0xbfffca28) in action #2 dtrace: error on enabled probe ID 1 (ID 36: profile:::profile-997): invalid address (0xbfffcb58) in action #2 The script is trying to determine the hot paths through initialization of firefox (up to main), e.g. Any suggestions on how to avoid the non-paged memory errors above? I'd recommend using Instruments and/or Shark for such profiles. The DTrace profile probe cannot give you this information at this time, as ustack() is not effective from the environment where profile probes get triggered. If I remember correctly that's due to not being able to take page faults in that environment. PS: <perfoptimization-dev@lists.apple.com> might be a better place to hit people more specialized towards performance work. This email sent to site_archiver@lists.apple.com