Comment 1 amehrega 2006-09-28 16:04:18 EDT

*** This bug has been marked as a duplicate of 158378 ***

Comment 2 Eugene Chan 2006-09-28 17:18:21 EDT

This problem looks like a regression from the introduction of the auto_generated_filter_set

<option key="org.eclipse.hyades.trace.ui.ATTR_FILTER_SET" value="auto_generated_filter_set"/>

When I profile to file in TPTP 430 and import into TPTP 421 workbench, I can see the problem in TPTP 421 workbench.
However, If I profile to file from 421 and import into TPTP 430, I don't see the problem anymore.
Both scenario was run using 430 Win RAC.

I will attach the profile files used

Comment 3 Eugene Chan 2006-09-28 17:18:52 EDT

Created attachment 51122 [details]
profile file generated from 430 workbench

Comment 4 Eugene Chan 2006-09-28 17:19:09 EDT

Created attachment 51123 [details]
profile file generated from 421 workbench

Comment 5 amehrega 2006-09-28 17:42:35 EDT

Alexander introduced these changes.

Comment 6 Guru Nagarajan 2006-09-28 17:57:01 EDT

Let me try and restate this issue as I understand it - correct me If I am wrong
a) In TPTP 43 - you have a "default" profile filter set that excludes "org.*" and that causes no data collection.
b) In case when you profile using TPTP 421 its all good and when you import the data into TPTP43 Workbench and when you re-run the profiler with the default filters (the default filter set is now not Org.* to be excluded) and the right data is collected.
So if the above is tru then - the change Alexander has to make is to make the chnage to the default filter set.

Comment 7 Eugene Chan 2006-09-28 18:11:52 EDT

(In reply to comment #6)
> Let me try and restate this issue as I understand it - correct me If I am wrong
> a) In TPTP 43 - you have a "default" profile filter set that excludes "org.*"
> and that causes no data collection.
> b) In case when you profile using TPTP 421 its all good and when you import the
> data into TPTP43 Workbench and when you re-run the profiler with the default
> filters (the default filter set is now not Org.* to be excluded) and the right
> data is collected.
> So if the above is tru then - the change Alexander has to make is to make the
> chnage to the default filter set.
> 
(a) is correct, I am not quite sure what you mean in (b)
The main problem is profile a simple HelloWorld application (which contains no java package) shows no data in statistics views when using default filter set, and Memory, Execution and Coverage analysis enabled. 

Running the same profile in 421 package correctly shows profiling data of HelloWorld application under '(default package)' in memory, execution and coverage statistics views.

When I profile to file with the exact same profiling filter and options in 430, I see the profiling data is much smaller than I expected, when compared to the same scenario in 421.

Comment 8 Alexander Simbirtsev 2006-09-29 08:41:42 EDT

I still think this is a duplicate of the #158580.
And as I can't find changes from fix to #158580 in CVS despite the bug is marked as fixed, the bug has a chance to be resolved once those changes really get to CVS.

Correct me if there's a misunderstanding from my side. 

Comment 9 Guru Nagarajan 2006-09-29 10:31:32 EDT

*** This bug has been marked as a duplicate of 158580 ***

Comment 10 Eugene Chan 2006-09-29 10:52:56 EDT

I will wait for the next build containing the fix and re-run the scenario again and comment here with results.

Comment 11 Eugene Chan 2006-11-16 15:03:14 EST

verified in 4.3i3 TP2 candidate and close bug