Eclipse Community Forums
Forum Search:

Search      Help    Register    Login    Home
Home » Eclipse Projects » Test and Performance Tools Platform (TPTP) » call stack problems (retry)
call stack problems (retry) [message #136067] Tue, 23 September 2008 17:33 Go to next message
andrea is currently offline andrea
Messages: 16
Registered: July 2009
Junior Member
Hi Eugene,

thx for your help but unfortunately, it doesn't work.
I try to explain my setting: I have a class A in a package p. I setting
options I selected exe time analysis and in edit of java profiling JRE 1.5
or newer I setted "p*" in class column and "*" in method name, finally I
selected "include" in column Rule.
Once profiling is completed I select exe time analysis/open with/execution
statistics obtaing correctly every views except call stack. I can see
thread view, for instance, and expand every node but call stack view is
empty. Notice thate I open call stack view starting from main menu
windows/show view/other/call stack.

What is incorrect?

Thx again,
Andrea
Re: call stack problems (retry) [message #136099 is a reply to message #136067] Tue, 23 September 2008 19:20 Go to previous messageGo to next message
Santi Ontañón is currently offline Santi Ontañón
Messages: 3
Registered: July 2009
Junior Member
Not sure if I understand what you are saying. But if I understand you
properly the windows you are opening (Call Stack) is only meaningful
during debugging. I'm not sure what are you expecting to see there after
profiling, since the "call stack" only makes sense in the middle of an
execution.
Re: call stack problems (retry) [message #136144 is a reply to message #136099] Wed, 24 September 2008 06:19 Go to previous messageGo to next message
andrea is currently offline andrea
Messages: 16
Registered: July 2009
Junior Member
Santi Ontañón wrote:

> Not sure if I understand what you are saying. But if I understand you
> properly the windows you are opening (Call Stack) is only meaningful
> during debugging. I'm not sure what are you expecting to see there after
> profiling, since the "call stack" only makes sense in the middle of an
> execution.
this is a test...

(my previous replies haven't been attached, I'm going to search what
doesn't work)
andrea
Re: call stack problems (retry) [message #136153 is a reply to message #136099] Wed, 24 September 2008 08:24 Go to previous messageGo to next message
andrea is currently offline andrea
Messages: 16
Registered: July 2009
Junior Member
Santi Ontañón wrote:

> Not sure if I understand what you are saying. But if I understand you
> properly the windows you are opening (Call Stack) is only meaningful
> during debugging. I'm not sure what are you expecting to see there after
> profiling, since the "call stack" only makes sense in the middle of an
> execution.
Thx Santi,

your speech is surely correct, but is there a way to stop execution of
profiler? That is: can it be used as a debugger? Can we set any
breakpoints?

What I'm going to get is tracing all the statements executed starting from
the beginnig to the end of the procedure. This task is in some way
obtained, for instance, expanding every node in thread windows. What I
wish is a sequence of all theese method callings possibly with the line
number.

So, I thought call stack was a suitable way, but as you fairly say, maybe
it's rather a way to get informations in a kind of debug mode.

Is it possible collect informations about the whole callings of methods,
that is, a rearragging what I see in thread window?

thx again
Andrea
Re: call stack problems (retry) [message #136401 is a reply to message #136153] Fri, 26 September 2008 20:48 Go to previous messageGo to next message
Eugene Chan is currently offline Eugene Chan
Messages: 287
Registered: July 2009
Senior Member
Hi Andrea,

The Call Stack view is designed to be used with Thread Analysis view, Call
Stack view shows a call stack of a thread selected in Thread Analysis view.
It has nothing to do with Execution Statistics.

If you want to understand the execution flow of your application, consider
the Call Tree tab under the Execution Statistics view which shows you a tree
presentation of your application execution.

It is not recommend to use profiler and debugger together as the debug
process will give misleading performance data of your application.eg. in
time measurement.

Eugene


"andrea " <ascarpa@dsi.unive.it> wrote in message
news:6636fa8dd016d89b107ab782185bf767$1@www.eclipse.org...
> Santi Onta
Re: call stack problems (retry) [message #136458 is a reply to message #136401] Sat, 27 September 2008 05:14 Go to previous messageGo to next message
andrea is currently offline andrea
Messages: 16
Registered: July 2009
Junior Member
thx Eugene...

call tree tab contains all I want to know... But is there a way to see it
in a "customizable" manner? I try to explain better: is there a way to
capture informations contained in call tree table in order to arrange
them, for instance, as a plain text without expanding every node?

Thx again
Andrea

> Hi Andrea,

> The Call Stack view is designed to be used with Thread Analysis view, Call
> Stack view shows a call stack of a thread selected in Thread Analysis view.
> It has nothing to do with Execution Statistics.

> If you want to understand the execution flow of your application, consider
> the Call Tree tab under the Execution Statistics view which shows you a tree
> presentation of your application execution.

> It is not recommend to use profiler and debugger together as the debug
> process will give misleading performance data of your application.eg. in
> time measurement.

> Eugene


> "andrea " <ascarpa@dsi.unive.it> wrote in message
> news:6636fa8dd016d89b107ab782185bf767$1@www.eclipse.org...
>> Santi Ontañón wrote:
>>
>>> Not sure if I understand what you are saying. But if I understand you
>>> properly the windows you are opening (Call Stack) is only meaningful
>>> during debugging. I'm not sure what are you expecting to see there after
>>> profiling, since the "call stack" only makes sense in the middle of an
>>> execution.
>> Thx Santi,
>>
>> your speech is surely correct, but is there a way to stop execution of
>> profiler? That is: can it be used as a debugger? Can we set any
>> breakpoints?
>>
>> What I'm going to get is tracing all the statements executed starting from
>> the beginnig to the end of the procedure. This task is in some way
>> obtained, for instance, expanding every node in thread windows. What I
>> wish is a sequence of all theese method callings possibly with the line
>> number.
>>
>> So, I thought call stack was a suitable way, but as you fairly say, maybe
>> it's rather a way to get informations in a kind of debug mode.
>>
>> Is it possible collect informations about the whole callings of methods,
>> that is, a rearragging what I see in thread window?
>> thx again
>> Andrea
>>
Re: call stack problems (retry) [message #136468 is a reply to message #136458] Mon, 29 September 2008 13:18 Go to previous messageGo to next message
Eugene Chan is currently offline Eugene Chan
Messages: 287
Registered: July 2009
Senior Member
Hi Andrea,

Unfortunately, there is currently no report/export support on the call tree
nor the execution flow table view for your need. Please open a feature
request on TPTP bugzilla system
( https://bugs.eclipse.org/bugs/enter_bug.cgi?product=TPTP%20P rofiling) if
you would like to have this feature support considered in the next feature
release.

Eugene

"andrea " <ascarpa@dsi.unive.it> wrote in message
news:badea0b86fe1a38b964cf08fa84d6c8e$1@www.eclipse.org...
> thx Eugene...
> call tree tab contains all I want to know... But is there a way to see it
> in a "customizable" manner? I try to explain better: is there a way to
> capture informations contained in call tree table in order to arrange
> them, for instance, as a plain text without expanding every node?
>
> Thx again
> Andrea
>
>> Hi Andrea,
>
>> The Call Stack view is designed to be used with Thread Analysis view,
>> Call Stack view shows a call stack of a thread selected in Thread
>> Analysis view. It has nothing to do with Execution Statistics.
>
>> If you want to understand the execution flow of your application,
>> consider the Call Tree tab under the Execution Statistics view which
>> shows you a tree presentation of your application execution.
>
>> It is not recommend to use profiler and debugger together as the debug
>> process will give misleading performance data of your application.eg. in
>> time measurement.
>
>> Eugene
>
>
>> "andrea " <ascarpa@dsi.unive.it> wrote in message
>> news:6636fa8dd016d89b107ab782185bf767$1@www.eclipse.org...
>>> Santi Onta
Re: call stack problems (retry) [message #136478 is a reply to message #136468] Mon, 29 September 2008 17:45 Go to previous message
andrea is currently offline andrea
Messages: 16
Registered: July 2009
Junior Member
Thx so much Eugene.

I'll send my request at address in your message.

Bye,
Andrea
Previous Topic:tracing execution
Next Topic:eclipse freezing while profiling
Goto Forum:
  


Current Time: Mon Oct 20 11:32:00 GMT 2014

Powered by FUDForum. Page generated in 0.03009 seconds
.:: Contact :: Home ::.

Powered by: FUDforum 3.0.2.
Copyright ©2001-2010 FUDforum Bulletin Board Software