Community
Participate
Working Groups
Currently the Linux Tools profiling framework puts all the profiling tools directly in the Profile As menu. This is inconsistent with how Run as... and Debug as.. which lists a C/C++ Executable. To make Profiling framework consistent, there should be a single Profile As... -> C/C++ Executable which then opens up to show the current Profile options (e.g. Profile Memory, Profile Timing, Profile Coverage). A bonus idea would be to create launch profiles for each Run As.. configuration such that the program arguments and environment variable settings would be transferred automatically. This may be difficult and should be put in its own bug (i.e. what to do when multiple configurations exist..use the last one on the run??)
After some experimenting, it is not possible to have a single Profile As... menu item that opens into multiple items with the current Eclipse launch framework in place. I am revising this to be the second part of my initial proposal. The Local C/C++ Application run/debug launch should add profile as one of the modes. Furthermore, the CDT launch configuration would have to be altered to: 1. Remove the Debugger page when in profile mode 2. Override the actual launch to use a Profiling provider delegate 3. Create a Profiler tab to replace the Debugger tab. The Profiler tab would have radio buttons to choose the type of profiling and then have a combo box to select the tool. The additional tabs would show up on this page, based on the combo box. This would present a shared configuration so any arguments/env variables would apply to debugging, running, and profiling. It would keep the Profile As.. menu from being cluttered because every type of launch (e.g. remote vs process on system ) might eventually require a launch configuration for each profiling type (e.g. Remote C/C++ Application Memory Profiling). By default, the profiling type would be Timing and Perf. Users who just want to profile their app will get a timing break-down and don't have to do any set-up. The short-cut presented to them would be the Local C/C++ Application which they should be familiar with after using the CDT for running and debugging. The preferences for profiling type could still apply and would be used when picking radio buttons. Comments/issues?
Jeff, after all the work in this area is there anything else pending from this bug or we can close it and open more specific ones for what's left.
(In reply to comment #2) > Jeff, after all the work in this area is there anything else pending from > this bug or we can close it and open more specific ones for what's left. We can close it and open new bugs as needed. This bug is actually a duplicate of 391608 *** This bug has been marked as a duplicate of bug 391608 ***
