Hi,
Make sure you use single quotes in your shell around wildcards, else the
shell will try to expand them to files in the current directory, e.g., you need
to do:
lttng enable-event -u 'system_event*' -c channel0 -s misc_data
This could very well explain why sometimes your events don't get
Hi all,
I checked __cyg_profile_func_enter implementation.
The caller address is recorded into call_site field.
Does anyone know how to let babeltrace show the call_site into
"func/offset" format instead of the running virtual address?
B.R.
Changcheng
_
Hi Changcheng,
This is not currently supported by Babeltrace. It could probably be done
the same way we do it with the "ip" and "vpid" contexts in the debug-info
component class but it's not done yet.
Thanks,
Francis
Le mer. 1 juill. 2020, à 11 h 58, Liu, Changcheng via lttng-dev <
lttng-dev@lis
On 12:25 Wed 01 Jul, Francis Deslauriers wrote:
>Hi Changcheng,
>This is not currently supported by Babeltrace. It could probably be
>done the same way we do it with the "ip" and "vpid" contexts in the
>debug-info component class but it's not done yet.
>Thanks,
>Francis
@Fr
Thanks a lot. I will try single quotes but it may take hours get the result.
Yesterday, I enabled the verbose option ,and found the following message "UST
app reply event failed. Application died (in add_event_ust_registry() at
ust-app.c:5405)" and "UST app notify socket unregister 34 (in
ust_a
