Some Eclipse Foundation services are deprecated, or will be soon. Please ensure you've read this important communication.

Bug 199601

Summary: Incorrect help content for Profiling and Logging preferences
Product: z_Archived Reporter: Valentina Popescu <popescu>
Component: TPTPAssignee: jkubasta
Status: CLOSED FIXED QA Contact:
Severity: normal    
Priority: P1 CC: ewchan, jkubasta
Version: unspecifiedKeywords: plan
Target Milestone: ---   
Hardware: PC   
OS: Windows XP   
Whiteboard: closed460
Attachments:
Description Flags
Changes to setting profiling preferences
none
Patch for broken csh link to setting logging preferences none

Description Valentina Popescu CLA 2007-08-10 12:04:41 EDT
I was trying to find out if the Agent Controller port is documented so I pressed F1 while on the Profiling and Logging preference page ( have the Profiling and logging item selected and in focus in the preferences tree) . Issues that I found :

1. Setting logging preferences link available at the beginning of the page is broken.

2. Navigate Setting profiling preferences link
In section 3, read this :
Use this pane to: 
- Enable or disable profiling or logging >>>>( this is incorrect, should be taken out, this option was removed a while ago )
- Change the default project name of a new profiling session. >>> Add some more description ?.. such as : this project will be used to stored the profiling data under the current workspace, if you choose to save the data after profiling an application.
- Specify whether to show helpful tips about profiling. 
- If you are not using a local deployment, specify the port number that the agent uses to connect to the Agent Controller. >>>>> Again, this is not true; this port is used for local development as well. As I discovered through trial, this port number is used when profiling an application through a launch configuration where the Hosts tab is not available, such as Java Application )
More on this : The 'Agent controller local port' preference is used when the port 
information is not made available with the profile launch configuration. As 
an example, profiling a Java application within your workspace will make use 
of this port information since no host/port information is specified with 
this launch wizard.
If you profile an application as an external Java app, there is a Host tab 
on the launch configuration where you specify the host ( localhost or a 
remote machine ) AND the port number. In this case, this port number will be 
used to connect to that host, the preference page port will be ignored.
- Select Appearance (and the items below it) to change the resources appearing in the Profiling Monitor view, the colors in the execution flow graph, and the amount of data displayed on each page of the Sequence Diagram. >>> The 'to change the resources appearing in the Profiling Monitor view' should be removed, this is not available anymore as an option
Comment 1 Valentina Popescu CLA 2007-08-10 12:07:53 EDT
setting priority to P1 since this part of the documentation is misleading and should be fixed as soon as possible
Comment 2 jkubasta CLA 2007-10-26 09:17:06 EDT
Created attachment 81260 [details]
Changes to setting profiling preferences
Comment 3 jkubasta CLA 2007-10-26 09:17:58 EDT
Valentina, would you please review the patch?  (I still have to fix the logging link)
Comment 4 jkubasta CLA 2007-11-19 22:27:41 EST
Changes checked into Head
Comment 5 jkubasta CLA 2007-11-22 18:07:51 EST
F1 link still broken
Comment 6 jkubasta CLA 2008-02-26 19:32:26 EST
Created attachment 90814 [details]
Patch for broken csh link to setting logging preferences
Comment 7 jkubasta CLA 2008-02-26 19:35:40 EST
patches committed to Head
Comment 8 Paul Slauenwhite CLA 2009-06-30 13:36:19 EDT
As of TPTP 4.6.0, TPTP is in maintenance mode and focusing on improving quality by resolving relevant enhancements/defects and increasing test coverage through test creation, automation, Build Verification Tests (BVTs), and expanded run-time execution. As part of the TPTP Bugzilla housecleaning process (see http://wiki.eclipse.org/Bugzilla_Housecleaning_Processes), this enhancement/defect is verified/closed by the Project Lead since this enhancement/defect has been resolved and unverified for more than 1 year and considered to be fixed. If this enhancement/defect is still unresolved and reproducible in the latest TPTP release (http://www.eclipse.org/tptp/home/downloads/), please re-open.
Comment 9 Paul Slauenwhite CLA 2009-06-30 14:19:10 EDT
As of TPTP 4.6.0, TPTP is in maintenance mode and focusing on improving quality by resolving relevant enhancements/defects and increasing test coverage through test creation, automation, Build Verification Tests (BVTs), and expanded run-time execution. As part of the TPTP Bugzilla housecleaning process (see http://wiki.eclipse.org/Bugzilla_Housecleaning_Processes), this enhancement/defect is verified/closed by the Project Lead since this enhancement/defect has been resolved and unverified for more than 1 year and considered to be fixed. If this enhancement/defect is still unresolved and reproducible in the latest TPTP release (http://www.eclipse.org/tptp/home/downloads/), please re-open.