Skip to contentSkip to conversation

Progress on base address outstanding issues

DISCUSSION Marc-André Laperle 2 participants 2 messages May 20, 2014 – May 22, 2014 1 message not in the archive

lore
Share & tools
lore

A message that is not in the archive (sent off-list or not yet received): [email protected]

#1 lore raw

Hi Mathieu,

I actually just started to use this feature in TMF so that we can handle libraries properly when showing call stacks (cygprofile). Hopefully this won't be removed :) Maybe I could look into the issue in a few weeks but it's likely that someone with better knowledge of LTTng's internals would come up with a fix much faster.

Regards,
Marc-Andre

Quoted 16 lines · Mathieu Desnoyers

Hi,

We are currently revisiting the open issues before the 2.5 release cycle, and we are wondering if there has been any progress on bug http://bugs.lttng.org/issues/745 ?

This feature is currently "experimental", but buggy (triggers deadlocks). Until we have a fix for this, it will stay experimental, and if there is no further progress on this front, we will mark it for removal for the 2.6 release cycle (around August 2014).

Thank you,

Mathieu

#2 lore raw
In reply to a message not in the archive

Hi Mathieu,

We use this feature in the new Codebench 2014.05 release (for cyg-profile symbol resolution and ust-tracepoint source line lookup). We will do what we can to make it stable and turn it into a fully supported feature.

I'm currently busy finding out why LTTng 2.4 userspace tracing with Yocto 1.6 on ARM(qemuarm) is not working properly.
( ust-tracepoints emitted from shared objects are never set into active state and thus not recorded :-[ ).

Once I'm done with that I will look into the deadlock issue.

--
Thanks,
Paul

Quoted 16 lines · Mathieu Desnoyers

Hi,

We are currently revisiting the open issues before the 2.5 release cycle, and we are wondering if there has been any progress on bug http://bugs.lttng.org/issues/745 ?

This feature is currently "experimental", but buggy (triggers deadlocks). Until we have a fix for this, it will stay experimental, and if there is no further progress on this front, we will mark it for removal for the 2.6 release cycle (around August 2014).

Thank you,

Mathieu

Signature · 3 lines
Paul Woegerer, SW Development Engineer
Sourcery Analyzer <http://go.mentor.com/sourceryanalyzer>
Mentor Graphics, Embedded Software Division