Andrey Dobrovolskiy(deleted)
|
Re: The application profiler doesn't show call count information
|
Andrey Dobrovolskiy(deleted)
10/21/2014 4:29 PM
post112091
|
Re: The application profiler doesn't show call count information
/de/profiler is of course a /dev/profiler
P.S. My application has multiple threads and runs on a dual core processor (shown as CPU 0 & 1 in kernel traces).
Probably this could lead to some side effecst? If I'm not wrong I saw a "know issue" with running sampling and call
count profiling on multiprocessor systems. Though even if it's the case the worst thing I can expect is that I won't see
profiling info for the code, which was executed on the second CPU core...
|
|
|
Elena Laskavaia
|
Re: The application profiler doesn't show call count information
|
Elena Laskavaia
11/28/2014 11:36 AM
post112481
|
Re: The application profiler doesn't show call count information
I tested different options and it all works from me - running from IDE,
attaching to a process, or doing postmortem.
Make sure that pass -p option to both compiler and linker.
If it still does not work use postmortem import (set var PRODIR instead,
then import gmon.out.* file in IDE).
If you still don't see call graph if doing postmortem - it means
something really went wrong with instrumentation.
On 14-10-21 04:22 PM, Andrey Dobrovolskiy wrote:
> Hi Shawn,
>
> I want to profile by attaching to the running process. I've created a profiler configuration for Sampling and Call
Counting, provided path th the shared libraries and source code files.
>
> What happens after I start profiling session is that I do see a live profiling process, with all the function names
and their location into the source files. After compiling with -gdwarf-2 flag I'm even able to switch to the particular
source and see CPU time distribution over the code lines (though to me it looks to be improper).
>
> What's missing is the call graph and hit count information. The latter is present but only for the node named <
filtered> so I would assume it's rather some code from uninstrumented library or a kernel one. Concerning call count I
must add that among other functions listed in profiling results there ones called _mcount_ and mcount, which I interpret
as a sign that the code does have instrumentation.
>
> For me it's completely a mistery what's going on behind the IDE. As far as I understand after setting a QCONN_PROFILER
variable to /de/profiler I should have redirected profiling statistics to the IDE, but how can I check that this is
really the case and I'm not still dealing with a plain Sampling profiler approach?
>
> Thank you & regards,
> Andrey
>
>
>
> _______________________________________________
>
> QNX Momentics Community Support
> http://community.qnx.com/sf/go/post112090
> To cancel your subscription to this discussion, please e-mail momentics-community-unsubscribe@community.qnx.com
|
|
|