Re: [lttng-dev] Getting function names with lttng-ust-cyg-profile.so

2013-09-11 Thread Amit Margalit
m Date: 09/11/2013 03:24 PM Subject: Re: [lttng-dev] Getting function names with lttng-ust-cyg-profile.so On 09/11/2013 11:12 AM, Amit Margalit wrote: I agree with Paul, that no redundant data gets replicated with his approach, and my only concern is that this approach really forces a viewer

Re: [lttng-dev] Getting function names with lttng-ust-cyg-profile.so

2013-09-11 Thread Woegerer, Paul
t; **From:**"Woegerer, Paul" > **To:**Matthew Khouzam > **Cc: **lttng-dev , Mathieu > Desnoyers > **Date:**09/10/2013 06:47 PM > **Subject:**Re: [lttng-dev] Getting function names with > lttng-ust-cyg-pro

Re: [lttng-dev] Getting function names with lttng-ust-cyg-profile.so

2013-09-11 Thread Amit Margalit
mit Margalit IBM XIV - Storage Reinvented XIV-NAS Development Team Tel. 03-689-7774 Fax. 03-689-7230 From: "Woegerer, Paul" To: Matthew Khouzam Cc: lttng-dev , Mathieu Desnoyers Date: 09/10/2013 06:47 PM Subject: Re: [lttng-dev] Getting function names with lttng-ust-c

Re: [lttng-dev] Getting function names with lttng-ust-cyg-profile.so

2013-09-10 Thread Matthew Khouzam
On 13-09-10 03:00 AM, Woegerer, Paul wrote: > Hi Alexandre, > > For trivial examples you can go with 'nm -CS' (or the like), but when > you start to use liblttng-ust-cyg-profile.so in combination with shared > objects you will need to record base address information as well (to > allow you map a v

Re: [lttng-dev] Getting function names with lttng-ust-cyg-profile.so

2013-09-10 Thread Woegerer, Paul
On 09/10/2013 05:37 PM, Matthew Khouzam wrote: > On 13-09-10 03:00 AM, Woegerer, Paul wrote: >> Hi Alexandre, >> >> For trivial examples you can go with 'nm -CS' (or the like), but when >> you start to use liblttng-ust-cyg-profile.so in combination with shared >> objects you will need to record bas

Re: [lttng-dev] Getting function names with lttng-ust-cyg-profile.so

2013-09-10 Thread Matthew Khouzam
Alex brought up an excellent point, these locations should be events since there can be address collisions. A default event for location with a payload of address and name would be sufficient I think. DlOpen will create many events then. On 13-09-10 11:15 AM, Matthew Khouzam wrote: > Hi Alex and

Re: [lttng-dev] Getting function names with lttng-ust-cyg-profile.so

2013-09-10 Thread Matthew Khouzam
Hi Alex and Mathieu, A year ago we discussed this and said iirc: "the addresses are a good first step, we'll do more later." and "It would be nice to dump the stabs into the metadata of the ctf trace" I would still maintain that this seems to be the way to go. A technical hurdle that is probably

Re: [lttng-dev] Getting function names with lttng-ust-cyg-profile.so

2013-09-10 Thread Amit Margalit
-7774 Fax. 03-689-7230 From: "Woegerer, Paul" To: , Mathieu Desnoyers Cc: lttng-dev Date: 09/10/2013 10:01 AM Subject: Re: [lttng-dev] Getting function names with lttng-ust-cyg-profile.so Hi Alexandre, For trivial examples you can go with 'nm -CS' (o

Re: [lttng-dev] Getting function names with lttng-ust-cyg-profile.so

2013-09-10 Thread Woegerer, Paul
Hi Alexandre, For trivial examples you can go with 'nm -CS' (or the like), but when you start to use liblttng-ust-cyg-profile.so in combination with shared objects you will need to record base address information as well (to allow you map a virtual memory address at a given point in time to offset

Re: [lttng-dev] Getting function names with lttng-ust-cyg-profile.so

2013-09-09 Thread Mathieu Desnoyers
We might want to investigate doing a side-program that gathers the executables on the system, and lookup the symbols from the ELF. We could save those in a bin/ subdirectory of a CTF trace. All we need is instrumentation of the dynamic linker, and to know the executable names associated with PIDs.

[lttng-dev] Getting function names with lttng-ust-cyg-profile.so

2013-09-09 Thread Alexandre Montplaisir
Hi all, I've recently started playing with liblttng-ust-cyg-profile.so (aka, getting UST events from -finstrument-functions), and I have to say it's pretty nifty! I haven't done any benchmarks, but it's certainly faster than the typical printf() that people use with it... However, in the resultin