Path: utzoo!utgpu!news-server.csri.toronto.edu!cs.utexas.edu!swrinde!zaphod.mps.ohio-state.edu!usc!trwind!venice!press
From: press@venice.SEDD.TRW.COM (Barry Press)
Newsgroups: comp.windows.ms
Subject: Re: Profiling and Peeking (Spy-type) tools for 3.0?
Keywords: 3.0 SPY PROFILER
Message-ID: <759@venice.SEDD.TRW.COM>
Date: 14 Aug 90 20:13:33 GMT
References: <1990Aug14.165728.8698@athena.mit.edu>
Reply-To: press@venice.sedd.trw.com (Barry Press)
Organization: TRW Systems Engineering & Development Division, Redondo Beach, CA
Lines: 26

In article <1990Aug14.165728.8698@athena.mit.edu> dedalus@athena.mit.edu (Lewis J. Gramer) writes:
>---------------------------------------------------------
>
>Is anyone out there aware of any more-sophisticated tools than the
>Microsoft Profiler for doing procedure call logging and perf-testing
>in Windows 3.0. For instance, a tool for protect or enhanced mode
>(real mode even??!) which might provide calling sequences, return
>values, and such. Also, are there any profilers that DON'T require
>munging the source-code with "ProfStart/Stop" type calls?

I wrote a profiler that worked under Win 2, picking apart the CV/Symdeb
interface from Windows after getting a hint what interrupt to look at.
It's possible that it still runs under real mode in Win 3 (I haven't bothered
to look, since the MS profiler does do something there).  There's no chance
that it runs as-is under WIn 3 in protected (standard or enhanced) modes, which
are the interesting cases.  It featured the ability to display the profiling
results (and zoom in on segments) from within Windows, so you could see the
effects as you did different things with your program.

MS was not willing to disclose the official details of the Win 2 interface
to me, and my guess is that trying again relative to the CV interface for
Win 3 would be a waste of time.  I would re-write the profiler for WIn 3
given that information, though.

-- 
Barry Press                                 Internet: press@venice.sedd.trw.com