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
De : Ikaheimonen, JP [mailto:jp_ikaheimo...@mentor.com]
Envoyé : 10 septembre 2013 07:41
As you can see, things easily get too complicated.
Currently in LTTng you can only disable events that are enabled in the first
place. In other words, an event is born disabled, as if 'lttng
-Message d'origine-
From: Julien Desfossez jdesfos...@efficios.com
The live trace reading mechanism offers guarantees that the viewer can never be
in a position where it has to assume that it can read the trace safely.
--
Could you clarify what you mean
On 10/09/13 03:45 AM, Amit Margalit wrote:
Hi,
The 2.4 release will include a major upgrade in the lttng-relayd to
support live trace viewing.
The trace viewers will be able to connect to a new TCP port on the relay
to list the tracing sessions currently established, attach to a session,
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
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
On 13-09-10 09:20 AM, Thibault, Daniel wrote:
-Message d'origine-
From: Julien Desfossez jdesfos...@efficios.com
The live trace reading mechanism offers guarantees that the viewer can never
be in a position where it has to assume that it can read the trace safely.
Hi Mathieu,
I recently created a high-level document to explain the prototype to my
colleagues. Maybe it is also useful to have that here on the mailinglist
(attached pdf).
Best,
Paul
On 08/27/2013 11:55 AM, Woegerer, Paul wrote:
...sorry, KMail was sending my draft without asking me first...
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 base address
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
I would +1 Ephemere, it goes well with live trace reading.
On 13-09-09 04:23 PM, Michel Dagenais wrote:
Don't forget, it's a beer that must be made in the Quebec province and
from a microbrewery. For 2.4, the beer must begin with the letter E.
Some help:
http://www.bieresduquebec.ca/bieres
Hi lttng-aficionados,
August 2013 summary:
- Stable release for 2.3 (Dominus Vobiscum) : the snapshots and crash
handler are the new features for this version. See announcement [1]
for more information.
- Bug tracker cleanup has been done. Thanks to all participants.
- Minor releases:
* Thibault, Daniel (daniel.thiba...@drdc-rddc.gc.ca) wrote:
I notice that the metadata of per-PID user-space traces has three
attributes which are dropped from the equivalent per-UID trace:
Per-PID trace:
env {
hostname = sds-dut-vb;
domain = ust;
tracer_name =
-Message d'origine-
De : Mathieu Desnoyers [mailto:mathieu.desnoy...@efficios.com]
Envoyé : 10 septembre 2013 16:18
And why is tracer_patchlevel dropped alongside the process-related
attributes?
Because different processes could use different tracer versions.
How is such a
I notice that the metadata of per-PID user-space traces has three attributes
which are dropped from the equivalent per-UID trace:
Per-PID trace:
env {
hostname = sds-dut-vb;
domain = ust;
tracer_name = lttng-ust;
tracer_major = 2;
tracer_minor = 3;
* Thibault, Daniel (daniel.thiba...@drdc-rddc.gc.ca) wrote:
-Message d'origine-
De : Mathieu Desnoyers [mailto:mathieu.desnoy...@efficios.com]
Envoyé : 10 septembre 2013 16:18
And why is tracer_patchlevel dropped alongside the process-related
attributes?
Because different
Date: Tue, 10 Sep 2013 11:28:53 -0400
From: Julien Desfossez jdesfos...@efficios.com
-Message d'origine-
The live trace reading mechanism offers guarantees that the viewer can
never be in a position where it has to assume that it can read the trace
safely.
* Yannick Brosseau (yannick.bross...@gmail.com) wrote:
On 2013-09-10 16:31, Mathieu Desnoyers wrote:
* Thibault, Daniel (daniel.thiba...@drdc-rddc.gc.ca) wrote:
-Message d'origine-
De : Mathieu Desnoyers [mailto:mathieu.desnoy...@efficios.com]
Envoyé : 10 septembre 2013 16:18
On 13-09-10 12:39 PM, Thibault, Daniel wrote:
Date: Tue, 10 Sep 2013 11:28:53 -0400
From: Julien Desfossez jdesfos...@efficios.com
-Message d'origine-
The live trace reading mechanism offers guarantees that the viewer can
never be in a position where it has to assume that it can
19 matches
Mail list logo
