lttng-dev.lists.lttng.org archive mirror
 help / color / mirror / Atom feed
From: Francis Deslauriers via lttng-dev <lttng-dev@lists.lttng.org>
To: Evan Galea <evanjamesgalea@gmail.com>
Cc: lttng-dev@lists.lttng.org
Subject: Re: [lttng-dev] Assertion tgt_fc failed when trying to trace callstack-user
Date: Thu, 5 Aug 2021 17:07:09 -0400	[thread overview]
Message-ID: <28459f83-bdae-a9c5-351f-96c9bc0de72d@efficios.com> (raw)
In-Reply-To: <CAA+-46qpk52j9B56wpvsJ=WvE-TX_83r+A6o7hqTxGeTLLS8cQ@mail.gmail.com>


[-- Attachment #1.1: Type: text/plain, Size: 2931 bytes --]

Hi Evan,

It turns out it's a Babeltrace 2 bug. Here the fix: 
https://review.lttng.org/c/babeltrace/+/6257.

It should be merged into the master and stable-2.0 branches soon.


Thank you for reporting the issue,

Francis


On 8/4/21 3:55 AM, Evan Galea wrote:
> Hi Francis, thanks for your reply. As it turns out, running babeltrace 
> on the file worked and I'm able to read the traces. I am running 
> babeltrace 1.5.8, lttng 2.12.4, lttng-tools 2.12.x stable, and lttng 
> modules 5.8.0-63. I attached the trace of the file.
>
>
> On Mon, Aug 2, 2021 at 8:56 AM Francis Deslauriers 
> <francis.deslauriers@efficios.com 
> <mailto:francis.deslauriers@efficios.com>> wrote:
>
>     Hi Evan,
>
>     On 8/1/21 5:11 AM, Evan Galea via lttng-dev wrote:
>>     Hi there
>>
>>     Thanks for help on my previous issue. I was able to get
>>     callstack-user to work and see it in my traces. However, in order
>>     to get it to run I needed to enable-event --kernel all. Is it
>>     necessary to have all kernel events enabled to run
>>     callstack-user? Or is it just one specific event?
>>
>>     When I try to run it without enabling all kernel events the
>>     command is accepted and it runs but I get the following error
>>     when trying to view my traces:
>>
>>      (╯°□°)╯︵ ┻━┻ ctf-meta-update-value-storing-indexes.c:65:
>>     update_field_class_stored_value_index(): Assertion `tgt_fc` failed.
>>     Aborted (core dumped)
>>
>>     What does this error mean? Should I just continue to enable all
>>     kernel events?
>
>     It's a Babeltrace 2 error. Now, we need to find out if the root
>     cause is the LTTng kernel tracer or Babeltrace2 itself.
>
>     What is the "one specific event" you're enabling that seems to
>     cause this issue?
>
>     Do you have access to a Babeltrace 1.5 build? if so, could you try
>     to read that same trace using it?
>
>     Could you please share a small trace reproducing this issue?
>
>     What version of LTTng-tools, LTTng-Modules, and Babeltrace2 are
>     you using?
>
>
>     Cheers,
>
>     Francis
>
>>
>>     My current command setup, not sure if relevant
>>
>>     lttng create &&
>>     lttng enable-channel mychannel --subbuf-size 100000000
>>     lttng enable-event --kernel --all &&
>>     lttng add-context -u -t vpid -t vtid -t procname &&
>>     lttng add-context --kernel --type callstack-user &&
>>     lttng add-context --kernel --type callstack-kernel &&
>>     lttng enable-event --jul jello
>>
>>     again thank you for your time
>>
>>     Evan Galea
>>
>>     _______________________________________________
>>     lttng-dev mailing list
>>     lttng-dev@lists.lttng.org  <mailto:lttng-dev@lists.lttng.org>
>>     https://lists.lttng.org/cgi-bin/mailman/listinfo/lttng-dev  <https://lists.lttng.org/cgi-bin/mailman/listinfo/lttng-dev>
>

[-- Attachment #1.2: Type: text/html, Size: 5855 bytes --]

[-- Attachment #2: Type: text/plain, Size: 156 bytes --]

_______________________________________________
lttng-dev mailing list
lttng-dev@lists.lttng.org
https://lists.lttng.org/cgi-bin/mailman/listinfo/lttng-dev

      parent reply	other threads:[~2021-08-05 21:07 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-08-01  9:11 Evan Galea via lttng-dev
2021-08-02 12:56 ` Francis Deslauriers via lttng-dev
     [not found]   ` <CAA+-46qpk52j9B56wpvsJ=WvE-TX_83r+A6o7hqTxGeTLLS8cQ@mail.gmail.com>
2021-08-05 21:07     ` Francis Deslauriers via lttng-dev [this message]

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=28459f83-bdae-a9c5-351f-96c9bc0de72d@efficios.com \
    --to=lttng-dev@lists.lttng.org \
    --cc=evanjamesgalea@gmail.com \
    --cc=francis.deslauriers@efficios.com \
    --subject='Re: [lttng-dev] Assertion tgt_fc failed when trying to trace callstack-user' \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link

This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).