RE: APPLE GUYS: Do you want Shark profiles of XCode when it hangs?
RE: APPLE GUYS: Do you want Shark profiles of XCode when it hangs?
- Subject: RE: APPLE GUYS: Do you want Shark profiles of XCode when it hangs?
- From: "Karan, Cem (Civ, ARL/CISD)" <email@hidden>
- Date: Wed, 24 Nov 2004 08:24:00 -0500
- Thread-topic: APPLE GUYS: Do you want Shark profiles of XCode when it hangs?
OK, from what Scott, Shawn, and you say, I'm going to go with the
premise that I should take Shark samples of everything when the system
hangs.
Scott, I can cause the hangs at will, but I'd like to be able to record
what was happening before I cause the hang to start. Right now I switch
between Shark and XCode "really fast" to try to capture the leading info
+ the material that caused the hang. Is there a way of setting up Shark
so that it is event triggered? By this I mean that Shark maintains a
FIFO that is some fixed size, with a snapshot being taken when an event
occurs like when the stop button gets pressed, etc (this is slightly
different from the 'instrument code and profile' route; I don't have the
ability to instrument your code). The idea is that I would have Shark
maintain a 30 second FIFO, waiting on a particular button to be pressed
(e.g., the stop button), then wait 15 seconds (or some other user
defined amount of time) and then take a snapshot of the FIFO. The
reason for this is that I know that I can cause a hang, but I also know
that it takes a long time to get to where it will hang. It would be
better to setup a simple script-like behaviour that triggers Shark's
sampling at the right time.
Thanks,
Cem Karan
> -----Original Message-----
> From: j o a r [mailto:email@hidden]
> Sent: Wednesday, November 24, 2004 1:15 AM
> To: Karan, Cem (Civ, ARL/CISD)
> Cc: email@hidden
> Subject: Re: APPLE GUYS: Do you want Shark profiles of XCode
> when it hangs?
>
>
> On at least one occasion I've received a note back from Apple
> engineering with the request to supply a Shark report to complement a
> sample that I already provided.
> One important difference between sample and shark is that you
> can have
> the report include _all_ processes running at the time of the
> sample -
> which makes it easier to get a good understanding of the over all
> system load when the profile was collected. For example, it might be
> interesting to see if the Window Server is busy or not.
>
> j o a r
>
> On 2004-11-23, at 23.10, Karan, Cem (Civ, ARL/CISD) wrote:
>
> > The subject line pretty much says it all; XCode has hung on
> me a few
> > times recently, and I finally had the brains to realize
> that I should
> > be running Shark against XCode any time that it hangs (maybe spin
> > control as well?) and to send in the reports to Apple. But I'm not
> > sure which of the performance tool's reports you guys would be
> > interested in. Any suggestions on what we should be running in the
> > background to get you guys the info that you need?
>
_______________________________________________
Do not post admin requests to the list. They will be ignored.
Xcode-users mailing list (email@hidden)
Help/Unsubscribe/Update your Subscription:
This email sent to email@hidden