BUG: Source Profiler in Visual C++ 5.0 Does Not Execute

 Last reviewed: October 10, 1997
Article ID: Q167804
The information in this article applies to:
  • Microsoft Visual C++, 32-bit Editions, version 5.0

SYMPTOMS

The Source Profiler, provided with Microsoft Visual C++ 5.0, may not execute from the Developer Studio. When attempting to profile, Developer Studio switches to the Profiler output window but the profiler tools are not executed and no output is produced.

CAUSE

This problem occurs because Developer Studio fails to create the correct environment paths for the spawned process and cannot find the profiler tools using the current path variables.

RESOLUTION

To work around this problem:

On Windows 95, add these directories to the PATH statement in your Autoexec.bat file: 

   PATH=C:\"Program Files"\DevStudio\SharedIDE\Bin;C:\"Program
   Files"\DevStudio\VC\Bin
On Windows NT, execute the System applet in Control Panel and select the Environment tab. Add the following directory names to the system's PATH environment variable (not the individual user's PATH): 

   C:\Program Files\DevStudio\SharedIDE\Bin;C:\Program
   Files\DevStudio\VC\Bin

STATUS

Microsoft has confirmed this to be a bug in the Microsoft products listed at the beginning of this article. We are researching this bug and will post new information here in the Microsoft Knowledge Base as it becomes available.

Additional query words: prep plist profile
Keywords : vcbuglist500 VwbIss
Version : 5.0
Platform : NT WINDOWS
Issue type : kbbug

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: October 10, 1997
© 1998 Microsoft Corporation. All rights reserved. Terms of Use.