Some Eclipse Foundation services are deprecated, or will be soon. Please ensure you've read this important communication.
Bug 196198 - Unknown entries in Execution Flow for Thread, Class and Method names
Summary: Unknown entries in Execution Flow for Thread, Class and Method names
Status: CLOSED WORKSFORME
Alias: None
Product: z_Archived
Classification: Eclipse Foundation
Component: TPTP (show other bugs)
Version: unspecified   Edit
Hardware: PC Windows 2000
: P3 critical (vote)
Target Milestone: ---   Edit
Assignee: Alexander N. Alexeev CLA
QA Contact:
URL:
Whiteboard:
Keywords:
: 199623 (view as bug list)
Depends on: 196013
Blocks: 191809
  Show dependency tree
 
Reported: 2007-07-11 13:52 EDT by jkubasta CLA
Modified: 2016-05-05 11:00 EDT (History)
6 users (show)

See Also:


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description jkubasta CLA 2007-07-11 13:52:53 EDT
See defect 196013,  step 8, Open Execution Flow. Under 'Thread
name'->main[xxxx]->main(java.lang.String[]), you should see an entry
"unknownXXXXX()", where XXXXX is a set of numbers (in this case 69256). 

The unknown entry comes from MethodEntry and MethodExit of a method that does
not have a MethodDef. The method is called during the pause period and so it's not sent to WB.
Comment 1 Asaf Yaffe CLA 2007-07-11 15:54:58 EDT
Please see my comment 10 to bug 196013. It may turn out to be a duplicate of bug 190687 or bug 193304.
Comment 2 jkubasta CLA 2007-07-12 08:25:38 EDT
Resolving as dup of 196013 as partial fix for 196013 was not delivered in 4.4.0.1

*** This bug has been marked as a duplicate of bug 196013 ***
Comment 3 Asaf Yaffe CLA 2007-07-12 08:57:23 EDT
Joana, we have determined that this bug is not a duplicate of 196013.

The root-cause is that classDef and methodDef information is not properly cached during "pause" and therefore not transmitted upon "resume". It would be better to leave this bug open so we can track it independently of bug 196013 (which was originally submitted to address an NPE in the workbench). 
Comment 4 jkubasta CLA 2007-07-12 08:59:21 EDT
Okay.  I am changing the target to 4.4.1.  If a 4.4.0.2 release is approved, this defect will be targeted to 4.4.0.2.
Comment 5 Eugene Chan CLA 2007-07-12 17:57:57 EDT
Note that in the scenario mentioned in bug 196013, 'unknown' is not shown in view if I start the Java proccess with vm options
 -agentlib:JPIBootLoader=JPIAgent:server=controlled;CGProf:execdetails=true
instead of 
-agentlib:JPIBootLoader=JPIAgent:server=controlled;CGProf


Comment 6 Stanislav Polevic CLA 2007-07-20 08:05:17 EDT
The problem is identified. 
CGProf caches thread/method entries/exits only in aggregated mode (aggregated mode is switched on by 'execdetails=true')

Guru, Asaf: Should this feature be addressed before new pause/resume logic will be available?

PS: Reassigning bug to Alex, cause I'm on vacation next week.
Comment 7 Asaf Yaffe CLA 2007-07-22 03:11:10 EDT
(In reply to comment #6)
> The problem is identified. 
> CGProf caches thread/method entries/exits only in aggregated mode (aggregated
> mode is switched on by 'execdetails=true')

IMHO, caching of method entry/exit events is not relevant for this defect. What needs to be cached is "classDef" and "methodDef" elements for new methods/classes identified while data collection is paused. These elements are constructed in the "New Method" event handler, not in method entry/exit event handlers.

This bug should be implemented as part of applying the updated design for supporting attach/detach/pause/resume use-cases.
Comment 8 Guru Nagarajan CLA 2007-08-23 17:40:11 EDT
*** Bug 199623 has been marked as a duplicate of this bug. ***
Comment 9 Alexander N. Alexeev CLA 2007-08-29 08:03:14 EDT
Isn't reproduced at 4.4.1-200708280100
Comment 10 jkubasta CLA 2007-08-30 08:58:53 EDT
Resolving since not reproducible
Comment 11 jkubasta CLA 2009-02-24 16:14:30 EST
closing