[
Date Prev][
Date Next][
Thread Prev][
Thread Next][
Date Index][
Thread Index]
[
List Home]
Re: [tracecompass-dev] Symbol names in call stack
|
Hi Deepankar,
I am really sorry about this, I realized I was using an experimental
branch, as there was no demand for the feature we implemented it for fun
but it is still a prototype. Now that we know people would use it, we
will strive to get it into master.
Best Regards,
Matthew
On 16-02-05 10:33 PM, Deepankar Sharma wrote:
> Hello Matthew,
>
> Thanks for the checklist. I was doing A, B but was doing doing C, D,
> E. I changed my scripts to start doing Step C as well after reading
> your email but havent had luck so far.
>
> I cant see my main programs call stack since its not built with
> instrumentation.
>
> Will continue digging into this to see if I can make some progress.
>
> Regards,
> Deepankar
>
> On Fri, Feb 5, 2016 at 9:53 AM, Matthew Khouzam
> <matthew.khouzam@xxxxxxxxxxxx <mailto:matthew.khouzam@xxxxxxxxxxxx>>
> wrote:
>
> Hi Deepankar,
>
> Thanks for the feedback.
>
> I did some profiling with trace compass but it was rudimentary.
> Here are
> some things on _my_ checklist.
>
> A- enable contexts... I always forget to enable contexts (VTID and
> PROCNAME)
> B- compile the shared objects in debug. There are more efficient
> ways to
> do it, but I wanted to see overall calls.
> C- make sure you have your BADDR (base address) tracepoints set up.
> D- I import the executable directly. This uses the button next to
> import
> mapping file.
> E- I use the nightly builds. Because I like to live dangerously.
>
> I think the company Efficios continued work on the callstack view.
>
> Also, can you see your main program's call stacks?
>
> On 16-02-05 08:37 AM, Deepankar Sharma wrote:
> > I have followed the instructions supplied here
> >
> http://help.eclipse.org/luna/index.jsp?topic=%2Forg.eclipse.linuxtools.lttng.help%2Fdoc%2FLTTng-UST-Analyses.html
> > to capture information about function enter and exits. Using the
> trace
> > captures I am able to see the call stack but unable to see the
> > function names. I tried to load the debug symbol binary file
> > (generated by using objcopy --only-keep-debug on my library).
> However
> > I still dont see symbol names.
> >
> > To investigate this issue I picked some of the symbols and
> grepped for
> > them in the nm output of my shared library and didnt find them. This
> > could possibly be because the symbols get remapped to a different
> > address at library load time since they come from a shared library.
> >
> > Does anyone have a working workflow where they get symbol names to
> > show up in callstacks generated from code in a shared library? Any
> > tips would be appreciated.
> >
> > Regards,
> > Deepankar
> >
> >
> > _______________________________________________
> > tracecompass-dev mailing list
> > tracecompass-dev@xxxxxxxxxxx <mailto:tracecompass-dev@xxxxxxxxxxx>
> > To change your delivery options, retrieve your password, or
> unsubscribe from this list, visit
> > https://dev.eclipse.org/mailman/listinfo/tracecompass-dev
>
> _______________________________________________
> tracecompass-dev mailing list
> tracecompass-dev@xxxxxxxxxxx <mailto:tracecompass-dev@xxxxxxxxxxx>
> To change your delivery options, retrieve your password, or
> unsubscribe from this list, visit
> https://dev.eclipse.org/mailman/listinfo/tracecompass-dev
>
>
>
>
> _______________________________________________
> tracecompass-dev mailing list
> tracecompass-dev@xxxxxxxxxxx
> To change your delivery options, retrieve your password, or unsubscribe from this list, visit
> https://dev.eclipse.org/mailman/listinfo/tracecompass-dev