Porting issue. The Second step. [message #126587] |
Mon, 17 March 2008 14:52 |
Eclipse User |
|
|
|
Originally posted by: ck2329.mail.ru
I'm happy to say that now Eclipse is able to show some info from my
target(linux mips) -heap and gc profilers are partitially in working state.
But anyway tptp is still extremely unstable.
Issue list:
1) It is impossible to connect threadProf - it fails on registering
MonitorWait event, MonitorWaited event etc capabilities on the JVM.
2) It is impossible to "attach to agent" from the first attempt - first i
should attach(i checked fileter - it is empy and named as "Default") -
then Detach from Agent - then attach again(now filter will be not empty
and named as "__JVMPI__" )
3) After first succesfull connecting to jvmti agent(server=enabled;
HeapProf) through AC and then stopping profiling session - it is
impossible to connect one more time.
4) If i choose "Run GC" then jvmti agent causes Segmentation fault
5) If i choose terminate process - then agent receives Kill signal - but
AC is already dead because of segmentation fault.
Please give some comments to the mentioned above if possible.
|
|
|
|
|
Re: Porting issue. The Second step. [message #126878 is a reply to message #126866] |
Wed, 19 March 2008 09:42 |
Eclipse User |
|
|
|
Originally posted by: ck2329.mail.ru
Asaf Yaffe wrote:
>> Issue list:
>> 1) It is impossible to connect threadProf - it fails on registering
>> MonitorWait event, MonitorWaited event etc capabilities on the JVM.
> Can you provide more information? Does it fail when invoking JVMTI
> SetEventNotificationMode? If so, what is the returned error code? If
> not, where does it fail?
> What JVM are you targeting (use 'java -version' on the target MIPS machine)?
It fails in CJVMTIInterface::RegisterEvent when calls to
m_pJVMTIInterface->AddCapabilities. return code is 98 - which means -
not_available. now im using latest cvm (rev62). Now im trying to
understand if cvm really doesnt support this event or something is wrong
with my request from martini side.
>>
>> 2) It is impossible to "attach to agent" from the first attempt - first
>> i should attach(i checked fileter - it is empy and named as "Default") -
>> then Detach from Agent - then attach again(now filter will be not empty
>> and named as "__JVMPI__" )
> Can you provide more information? What do you mean by "first attempt"?
> Where does it fail? Is this an Agent Controller issue? Agent issue?
> Martini issue?
As i said to get some results in Eclipse i should attach to agent[FIRST
ATTEMPT] - then Detach from Agent - then attach again[SECOND ATTEMPT].
Actully there is no failure on first attempt - i just cannot get any info
in eclipse. I tried both with server = enabled and controlled
>>
>> 3) After first succesfull connecting to jvmti agent(server=enabled;
>> HeapProf) through AC and then stopping profiling session - it is
>> impossible to connect one more time.
> Again, more information will be helpful (see previous question).
Current situation is a little bit different - i can connect - but
application seems to be frozen . according to your previous explanation i
applied patch https://bugs.eclipse.org/bugs/show_bug.cgi?id=186080 but it
works only for the first attach.
>>
>> 4) If i choose "Run GC" then jvmti agent causes Segmentation fault
> Can you provide a stack dump (preferably in debug mode)? If not, can you
> point to the module causing the crash?
>>
>> 5) If i choose terminate process - then agent receives Kill signal - but
>> AC is already dead because of segmentation fault.
> Again... stack dump...
Now on going
>>
>> Please give some comments to the mentioned above if possible.
>>
> We'll do our best :)
I see! Thanks for your suport, i'll try to help you - if i know the answer
for other user's quetion - i'll reply!
One more question - how can i get latest (4.5) sources - is it HEAD
revision on main repository or you have dedicated one ?
> Thanks,
|
|
|
|
Re: Porting issue. The Second step. [message #126918 is a reply to message #126904] |
Wed, 19 March 2008 13:45 |
Eclipse User |
|
|
|
Originally posted by: ck2329.mail.ru
Thanks . You are right prroblem was caused by can_get_monitor_info. I
turned it on on my JVM - no ThreadProfiler works.
I chacked threadProf on my sample app. And results are confusing. My app
is running very very slow with tptp profiler.I tried to run NetBeans
profiler on the same target - it is more then 10 times faster :-(.
Probably i can make tptp faster by specifiyng some kind of filter? Now i
use just default settings. Can i ?
|
|
|
|
|
|
|
Re: Porting issue. The Second step. [message #127027 is a reply to message #126968] |
Thu, 20 March 2008 06:50 |
Eclipse User |
|
|
|
Originally posted by: ck2329.mail.ru
I would like to perform following experiment:
I want to turn off all data transfer and check execution time in case of
internal (jvmti profiler) operations. What function should i stub for this?
Some more explanations - i want to leave only martini and some more
internal processing for JVM events. I want to exclude all XML related
operations. I need i t do determine if the great overhead is brought only
by XML or if some other(intenal) parts also bring some perfomance bottle
necks.
|
|
|
|
Re: Porting issue. The Second step. [message #127166 is a reply to message #127153] |
Fri, 21 March 2008 09:16 |
Eclipse User |
|
|
|
Originally posted by: ck2329.mail.ru
Hi Igor
Unfortunately standalone mode is not suitable for our puprpose.
I already made stubs in PrintXML file - according to my rough measurment
on Windows system this doesnt provide significant speed up.
I got follwoing results with thread profiler in standalone mode(just for
test):
without profiling - 4.1 sec
with profiling and xml output - 8.2 sec
with profiling and with stubs in printxml - 7.9
Thats it. I also try to test on our target system asap.
Anyway imho TPTP uses too complicated profiling chain - Eclipse - AC -
profiler - JPI - Martini - JVM ....
|
|
|
|
|
|
Powered by
FUDForum. Page generated in 0.02529 seconds