Thread: Visual Studio 2015 — CPU Usage Profiling Not Working?

  1. #1
    Registered User
    Join Date
    Aug 2015
    Posts
    1

    Visual Studio 2015 — CPU Usage Profiling Not Working?

    I recently upgraded from Visual Studio 2013 Community to Visual Studio 2015 Community.

    I've heavily relied on the "CPU Usage" Tool that can be found by doing the following:

    1. Click "Debug"
    2. Click "Start Diagnostic Tools without Debugging"
    3. Click "CPU Usage" Check box
    4. Click "Start" button

    When the program is complete, it is supposed to show you the functions and the time spent in each. What I get instead is just the name of my executable that I can keep expanding instead of seeing the function names -- It doesn't know the names of the functions.

    This worked fine on Visual Studio 2013... I would be able to see the function names and everything worked. I tried creating a new "test" solution/project to see whether this works and I get the same results: No function names.

    Does this work for anybody? I also installed VS2015 on a fresh development box and still have no results. This seems like Microsoft shipped with a Visual Studio bug.

    Note: I'm writing a C++ console application. I've tried this on debug and release builds and ensured that I'm building with debug information.

    You can see here how we don't see function names. Instead it just shows the name of the executable I'm debugging:
    -test-jpg
    Last edited by BobLoblaw465634; 08-09-2015 at 12:05 PM.

  2. #2
    C++まいる!Cをこわせ!
    Join Date
    Oct 2007
    Location
    Inside my computer
    Posts
    24,654
    I'd ask over at the MSDN forums. You'll likely get more responses there.
    Quote Originally Posted by Adak View Post
    io.h certainly IS included in some modern compilers. It is no longer part of the standard for C, but it is nevertheless, included in the very latest Pelles C versions.
    Quote Originally Posted by Salem View Post
    You mean it's included as a crutch to help ancient programmers limp along without them having to relearn too much.

    Outside of your DOS world, your header file is meaningless.

  3. #3
    Officially An Architect brewbuck's Avatar
    Join Date
    Mar 2007
    Location
    Portland, OR
    Posts
    7,396
    It is possible this is a bug in VS2015.

    Do you happen to be running Windows 8.1?
    Code:
    //try
    //{
    	if (a) do { f( b); } while(1);
    	else   do { f(!b); } while(1);
    //}

Popular pages Recent additions subscribe to a feed

Similar Threads

  1. Replies: 1
    Last Post: 08-08-2015, 01:02 PM
  2. profiling for memory usage
    By icegood in forum C Programming
    Replies: 6
    Last Post: 01-03-2013, 10:30 AM
  3. OutputDebugString not working in Visual Studio 2008
    By jw232 in forum Windows Programming
    Replies: 3
    Last Post: 07-02-2009, 07:13 PM
  4. Remote debug not working in Visual Studio 2003
    By Bassquake in forum Tech Board
    Replies: 12
    Last Post: 08-22-2008, 12:11 PM
  5. I can't get profiling to work with Visual Studio 6
    By Darkness in forum C++ Programming
    Replies: 7
    Last Post: 12-30-2004, 10:37 PM