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

Bug 201556

Summary:

[CGProf] unknow thread at veiw

Product:

z_Archived

Reporter:

Alexander N. Alexeev <analexee>

Component:

TPTP

Assignee:

Guru Nagarajan <guru.nagarajan>

Status:

CLOSED FIXED

QA Contact:

Severity:

normal

Priority:

CC:

analexee, asaf.yaffe, jkubasta

Version:

unspecified

Keywords:

plan

Target Milestone:

---

Hardware:

All

OS:

All

Whiteboard:

closed460

Attachments:

Description	Flags
fix, doesn't print etities in active state.	none

Description Alexander N. Alexeev

2007-08-29 08:14:06 EDT

Build ID: 4.4.1-200708280100

Steps To Reproduce:
1. Launch InOut in controlled mode. e.g. java
-agentlib:JPIBootLoader=JPIAgent:server=controlled:execdetails=true ;CGProf InOut

2. In Eclipse, open the profile dialog, create a new Attach entry for InOut,
and specify "Show execution flow graphical details" under Execution Time
Analysis (Agents tab).

3. Open the Execution Statistics view after the entry prompt is displayed in
the Profiling Console. Refresh the view until no additional data is shown.

4. Pause the agent
5. Press enter in the profiling console. 
6. Resume the agent
7. Press enter in the profiling console. 

8. Open Execution Flow. Under 'Thread
name'->main[xxxx] "unknown" thread appears

also unknown class and method can be found in other views

Comment 1 Alexander N. Alexeev

2007-08-29 08:20:41 EDT

This problem doesn't related to bug 196198.
Rootcause is that after resume agent sends methodEnter events for uninitialized entries from shadow stack, because it doesn't take into account is "active" state.

Comment 2 Alexander N. Alexeev

2007-08-29 08:24:41 EDT

Created attachment 77240 [details]
fix, doesn't print etities in active state. 

Please, review fix.

Comment 3 Asaf Yaffe

2007-08-29 09:01:40 EDT

Patch reviewed.

Comment 4 Guru Nagarajan

2007-08-30 18:15:30 EDT

Fix checked in. Pls validate in tomorrows build

Comment 5 Paul Slauenwhite

2007-12-19 07:59:20 EST

Please change the target to the 4.5 iteration when this Bugzilla was resolved.

Comment 6 Paul Slauenwhite

2009-06-30 13:27:37 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 7 Paul Slauenwhite

2009-06-30 14:18:28 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.