Path: utzoo!utgpu!news-server.csri.toronto.edu!cs.utexas.edu!uunet!efi!tim From: tim@efi.com (Tim Maroney) Newsgroups: comp.sys.mac.programmer Subject: Re: THINK Profiler Question (repost) Message-ID: <1990Aug17.211851.5896@efi.com> Date: 17 Aug 90 21:18:51 GMT References: Organization: Electronics For Imaging, Inc. Lines: 20 In article jackiw@cs.swarthmore.edu (Nick Jackiw) writes: >I'm having a horrible time trying to profile my code (THINK Pascal v.3.0 >on an 8M SE/30 under 6.0.3 Multifinder)--I keep crashing. If any one >can offer any suggestions, I'd be most grateful. > >Sometimes it crashes during what must be my DumpProfileToFile call, in >that a partial profile is generated. The stats collected in this partial >program are almost definitely wrong, and include (for instance) functions >which have never been called. I have had much the same experience with the THINK Pascal 3.1 profiler. It tells me that all my time is spent in routines which are not in fact called at all when I have the profiler activated -- and in many cases, are never called at all. For instance, it likes to tell me that I am spending a lot of time in the MacApp busy cursor VBL routine, although I have qBusyCursor set to zero and I have verified that the VBL task is not installed. I am using TP 3.0.1, MacApp 2.0, compiled with both MacApp debugger and LightsBug, with names, running under the THINK debugging environment with an 8 Meg Mac IIci.