Code::Blocks Forums

User forums => Using Code::Blocks => Topic started by: C:B_newbie on September 12, 2018, 11:10:11 pm

Title: Debug "mode" for Profiler
Post by: C:B_newbie on September 12, 2018, 11:10:11 pm

Greetings,

is anyone familiar with the Very Sleepy profiler on a Windows system?

If I let it sample over my C++ application (run from Code Blocks), it can not list the runtime of each function called within the application (it only shows cryptic code like [oxff293983] with some runtime percentage and time next to it).

In a tutorial, it is said that, after stopping the sampling, the profiler will not only show the function calls but also a visual display of the runtime "hot spots" with corresponding lines in the source code, "provided the profiled exetubale file contains debug information with reference to the source code file".

How do I make sure the last part is fulfilled? Do I have to manually execute the program with the command prompt?

Regards

Title: Re: Debug "mode" for Profiler
Post by: oBFusCATed on September 13, 2018, 01:01:52 am

Open project build options
1. enable debug info
2. make sure the strip option is not enabled

And also make sure that this profiler understands the debug info generated by your compiler (mingw on windows is not compatible with vc++)...

Title: Re: Debug "mode" for Profiler
Post by: BlueHazzard on September 13, 2018, 03:27:15 am

Quote

And also make sure that this profiler understands the debug info generated by your compiler (mingw on windows is not compatible with vc++)...

Sleepy profiler should be ok with most mingw code. I have used it to profile codeblocks some time ago. Sleepy profiler had some problems with some self compiled dlls, but i never figured out what the trouble was..