Bug 272534

Summary:	KDevelop says that profiled launch is not supported, but not why
Product:	[Applications] kdevelop	Reporter:	Wolfgang Bangerth <bangerth>
Component:	Profiles	Assignee:	kdevelop-bugs-null
Status:	RESOLVED FIXED
Severity:	normal
Priority:	HI
Version:	4.2.1
Target Milestone:	4.2.0
Platform:	Compiled Sources
OS:	Linux
Latest Commit:	http://commits.kde.org/kdevplatform/d1ec3ea2e009f092eee128f5bd5f4733fa170eb6	Version Fixed In:
Sentry Crash Report:

Description Wolfgang Bangerth 2011-05-05 14:57:25 UTC

Version:           4.2.1 (using KDE 4.6.0) 
OS:                Linux

When I go to "Run > Profile launch", all I get is an error box saying "The current launch configuration does not support the 'profile' mode." The problem is: I have no idea why not:
- Going through the "Run > Configure launches" dialog, I see no option that has
  anything to do with profiles -- I thought I may have to add a different
  launch configuration, for example, but there didn't seem to be anything in
  this direction
- I have both gprof and valgrind installed

The point is that I'm sure KDevelop has good reasons for the error message but it doesn't say which they are and how I can remedy them :-)


Some more digging:
- the error message is produced in kdevplatform/RunController::execute
- to the best of my knowledge, it happens because no launch for the
  'profile' id exists in LaunchConfiguration
Beyond this, my KDevelop source foo wanes...

Best
 Wolfgang

Reproducible: Always

Comment 1 Milian Wolff 2011-05-30 16:04:52 UTC

indeed, this should be disabled/removed until we have profile launches supported again

Comment 2 Aleix Pol 2013-10-08 00:34:25 UTC

Git commit d1ec3ea2e009f092eee128f5bd5f4733fa170eb6 by Aleix Pol.
Committed on 08/10/2013 at 00:31.
Pushed by apol into branch 'master'.

Remove unused Run > profile menu entry

Currently we had the menu entry but nobody using it. Technically it's
correct because whenever we'd get a profiler it would work automatically
but I'd say that also having the option but not being able to use
it is nothing but frustrating.

Commenting out the code until somebody puts some care into profiling
integration.

M  +7    -7    shell/runcontroller.cpp

http://commits.kde.org/kdevplatform/d1ec3ea2e009f092eee128f5bd5f4733fa170eb6