Code::Blocks Forums

User forums => Help => Topic started by: Audette on June 19, 2008, 09:48:41 am

Title: Profiler not working in windows
Post by: Audette on June 19, 2008, 09:48:41 am
Hello,

I am having a problem with running the profiler on a win xp machine. I have build my code using -g and -pg. But still when I go plugins -> code  profiler, the launching gprof pop up comes up and crashes. Does anyone have any ideas why this is happening.

I have tried the same code within Vista and after following the suggestions in the following thread the profiler worked. But no such luck with XP.
http://forums.codeblocks.org/index.php/topic,1272.0.html

Before you suggest, I have reinstalled MinGW and all the associated componenets. Even uninstalled and reinstalled the Code::Blocks program without any joy :(

Please help.
Title: Re: Profiler not working in windows
Post by: MortenMacFly on June 19, 2008, 10:15:47 am
Please help.
Which (exact) version of binutils you are using?
Title: Re: Profiler not working in windows
Post by: Audette on June 19, 2008, 10:19:55 am
The current release binutils 2.17.50

The MinGW was installed from the automated installer - Ver 5.1.4

on top of it, I have installed MSys 1.0.10 and GDB 6.8-3 (release candidate)
Title: Re: Profiler not working in windows
Post by: MortenMacFly on June 19, 2008, 10:27:40 am
The current release binutils 2.17.50
That's OK (later version(s) have bugs with gprof).

on top of it, I have installed MSys 1.0.10
Huh! This is most likely no good. You cannot and should not install MSYS on top of a compiler installation. Usually MSYS is a stand-alone "tool" which refers to the folder where GCC is installed via fstab. So this *might* be a reason.

Right... as a next step: Please try running gprof from the command line and not from within C::B. Does is crash then, too?
Title: Re: Profiler not working in windows
Post by: Audette on June 19, 2008, 11:08:16 am
Quote
Right... as a next step: Please try running gprof from the command line and not from within C::B. Does is crash then, too?

Nope - this seems to be working fine when called from the command line.

but there must be some way to get it working within Code::Blocks as well - right???