Mirror of the lttng-dev mailing list
 help / color / mirror / Atom feed
From: Kienan Stewart via lttng-dev <lttng-dev@lists.lttng.org>
To: Brian Hutchinson <b.hutchman@gmail.com>,
	lttng-dev@lists.lttng.org, yocto@lists.yoctoproject.org
Subject: Re: [lttng-dev] Using lttng-ust 2.13.6 from Yocto Kirkstone and getting weird segfault saying strlen_asimd.S can't be found.
Date: Thu, 11 Jul 2024 08:38:22 -0400	[thread overview]
Message-ID: <d30f1655-0efa-440a-ac17-fe82342f4556@efficios.com> (raw)
In-Reply-To: <CAFZh4h9iaCGdnDhxik9Qtq82f0MGU2eL+8nBa8qoCCJrH-xsGQ@mail.gmail.com>

Hi Brian,

On 7/11/24 8:33 AM, Brian Hutchinson via lttng-dev wrote:
 > ...
 >
 > I'm not sure about this, still trying to comprehend everything, but I
 > think my issue could be related to all this gcc TLS, heap, trampoline
 > talk here:
 >
 > https://www.mail-archive.com/lttng-dev@lists.lttng.org/msg13584.html
 > <https://www.mail-archive.com/lttng-dev@lists.lttng.org/msg13584.html>
 >
 > Regards,
 >
 > Brian
 >

You could try using lttng-ust 2.13.8, which includes a fix for the 
discussion you referenced.

https://github.com/lttng/lttng-ust/commit/5db715e800d9b721f48495a987cd26c25965e836

Please let us know if it doesn't solve it.

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

  reply	other threads:[~2024-07-11 12:38 UTC|newest]

Thread overview: 21+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-07-11  1:53 Brian Hutchinson via lttng-dev
2024-07-11 12:33 ` Brian Hutchinson via lttng-dev
2024-07-11 12:38   ` Kienan Stewart via lttng-dev [this message]
     [not found]     ` <CAFZh4h9hyQj0JV5_pA4tQyoB8hTAfkmWbmZ2jJW2Vcwk4NMVig@mail.gmail.com>
2024-07-12 14:17       ` Kienan Stewart via lttng-dev
     [not found]         ` <CAFZh4h8yk-u54wMGitXYYfPSYTwfdO=j8QVKSDqhCufbomHLrw@mail.gmail.com>
     [not found]           ` <CAFZh4h9veQ+jRHOF=UGsjBVV_CcrdNUp1g76273APryrbyM5yw@mail.gmail.com>
2024-07-12 19:21             ` Kienan Stewart via lttng-dev
2024-07-17  1:27     ` Brian Hutchinson via lttng-dev
2024-07-17 14:13       ` Kienan Stewart via lttng-dev
2024-07-17 16:27         ` Brian Hutchinson via lttng-dev
2024-07-18 14:27           ` Kienan Stewart via lttng-dev
2024-07-23  4:48             ` Brian Hutchinson via lttng-dev
     [not found]             ` <CAFZh4h-_ixamDD4hMMETXGx8oA6Dr_3R5eFBeQPusFnKHEXKGg@mail.gmail.com>
2024-07-24 16:04               ` Kienan Stewart via lttng-dev
2024-07-25 19:54                 ` Brian Hutchinson via lttng-dev
2024-07-29 19:03                   ` Kienan Stewart via lttng-dev
2024-07-30 12:40                     ` Brian Hutchinson via lttng-dev
2024-07-30 15:54                       ` Brian Hutchinson via lttng-dev
2024-07-30 15:55                         ` [lttng-dev] [yocto] " Khem Raj via lttng-dev
2024-07-30 16:31                           ` Brian Hutchinson via lttng-dev
2024-07-30 15:58                         ` [lttng-dev] " Kienan Stewart via lttng-dev
2024-08-21 12:51                           ` Brian Hutchinson via lttng-dev
2024-08-21 15:02                             ` Kienan Stewart via lttng-dev
2024-07-29 22:36                 ` Brian Hutchinson via lttng-dev

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=d30f1655-0efa-440a-ac17-fe82342f4556@efficios.com \
    --to=lttng-dev@lists.lttng.org \
    --cc=b.hutchman@gmail.com \
    --cc=kstewart@efficios.com \
    --cc=yocto@lists.yoctoproject.org \
    /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
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox