|
|
|
| Re: call stack problems (retry) [message #136153 is a reply to message #136099] |
Wed, 24 September 2008 08:24   |
 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 #136458 is a reply to message #136401] |
Sat, 27 September 2008 05:14 |
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
>>
|
|
|
|
|
Powered by
FUDForum. Page generated in 0.04469 seconds
] 
Search
Help
Register
Login
Home
