DOCERR: Minimal SDK Profiler Functions Required

 Last reviewed: July 23, 1997
Article ID: Q90791
3.10 WINDOWS kbtool kbprg kbdocerr

The information in this article applies to:

  • Microsoft Windows Software Development Kit (SDK) for Windows version 3.1

SYMPTOMS

The directions given in Chapter 10 of the Windows 3.1 SDK "Programming Tools" manual are followed, but no profiler output is generated.

CAUSE

The "Programming Tools" manual states the following on page 208: 

   2. Include in your application at least the two mandatory
      Profiler functions ProfStart() and ProfStop().

      ProfStart() indicates when you want Profiler to start
      sampling code; ProfStop() indicates when you want Profiler to
      stop sampling. Other Profiler functions are optional.
This is accurate but not complete. ProfStop() does stop sampling, but it does not write any output to the disk. Because of this, the Profiler appears to not work.

RESOLUTION

To get the Profiler to function completely, either a call to the Profiler function ProfFlush() must be made prior to the call to ProfStop(), or the function ProfFinish() should be used. The documentation would be more accurate if it stated that the minimum Profile application contained a call to ProfStart() and a call to ProfFinish(). ProfFinish() stops profile sampling and flushes the buffer (to disk).

Additional reference words: 3.10 docerr
KBCategory: kbtool kbprg kbdocerr
KBSubcategory: TlsPrf
Keywords : kb16bitonly

THE INFORMATION PROVIDED IN THE MICROSOFT KNOWLEDGE BASE IS PROVIDED "AS IS" WITHOUT WARRANTY OF ANY KIND. MICROSOFT DISCLAIMS ALL WARRANTIES, EITHER EXPRESS OR IMPLIED, INCLUDING THE WARRANTIES OF MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE. IN NO EVENT SHALL MICROSOFT CORPORATION OR ITS SUPPLIERS BE LIABLE FOR ANY DAMAGES WHATSOEVER INCLUDING DIRECT, INDIRECT, INCIDENTAL, CONSEQUENTIAL, LOSS OF BUSINESS PROFITS OR SPECIAL DAMAGES, EVEN IF MICROSOFT CORPORATION OR ITS SUPPLIERS HAVE BEEN ADVISED OF THE POSSIBILITY OF SUCH DAMAGES. SOME STATES DO NOT ALLOW THE EXCLUSION OR LIMITATION OF LIABILITY FOR CONSEQUENTIAL OR INCIDENTAL DAMAGES SO THE FOREGOING LIMITATION MAY NOT APPLY.

Last reviewed: July 23, 1997
© 1998 Microsoft Corporation. All rights reserved. Terms of Use.