Mirror of the lttng-dev mailing list
 help / color / mirror / Atom feed
From: Brian Hutchinson via lttng-dev <lttng-dev@lists.lttng.org>
To: Kienan Stewart <kstewart@efficios.com>
Cc: 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: Tue, 16 Jul 2024 21:27:25 -0400	[thread overview]
Message-ID: <CAFZh4h_pOCzpJ6ssdZ7ts3vSdJNfEtS+d+2Foi4qAY6oH0+VKw@mail.gmail.com> (raw)
In-Reply-To: <d30f1655-0efa-440a-ac17-fe82342f4556@efficios.com>


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

Hi Kienan,

On Thu, Jul 11, 2024 at 8:38 AM Kienan Stewart <kstewart@efficios.com>
wrote:

> 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
>

I updated to lttng-ust 2.13.8 as you suggested.  At first, I pulled in the
recipe from master branch of Yocto, but had the same problem as before
after rebuilding.

Next, I downloaded the 2.13.8 lttng-ust tarball from the lttng site and
setup a native build environment on my target and built lttng-ust 2.13.8
and my app as a second independent build method for sanity check.  I can
report that I get the exact same result as before this way too.

In both cases, I verified that I had the commit you referenced above.

I did a backtrace of the three threads captured in the coredump and show
them below in hopes it will shed light on what I need to try next.

(gdb) thread apply all backtrace

Thread 3 (Thread 0xffffbe7de7e0 (LWP 559)):
#0  syscall () at ../sysdeps/unix/sysv/linux/aarch64/syscall.S:38
#1  0x0000ffffbeef1bb8 in lttng_ust_futex (val3=0, uaddr2=0x0, timeout=0x0,
val=0, op=0, uaddr=0xffffbefd8000) at ../../../src/lib/lttng-ust/futex.h:56
#2  lttng_ust_futex_async (op=0, val=0, timeout=0x0, uaddr2=0x0, val3=0,
uaddr=0xffffbefd8000) at ../../../src/lib/lttng-ust/futex.h:88
#3  wait_for_sessiond (sock_info=0xffffbef6b638 <global_apps>) at
lttng-ust-comm.c:1761
#4  ust_listener_thread (arg=0xffffbef6b638 <global_apps>) at
lttng-ust-comm.c:1832
#5  0x0000ffffbe9206a8 in start_thread (arg=0xffffc1bd8687) at
pthread_create.c:442
#6  0x0000ffffbe98801c in thread_start () at
../sysdeps/unix/sysv/linux/aarch64/clone.S:79

Thread 2 (Thread 0xffffbdfce7e0 (LWP 560)):
#0  syscall () at ../sysdeps/unix/sysv/linux/aarch64/syscall.S:38
#1  0x0000ffffbeef1bb8 in lttng_ust_futex (val3=0, uaddr2=0x0, timeout=0x0,
val=0, op=0, uaddr=0xffffbefd7000) at ../../../src/lib/lttng-ust/futex.h:56
#2  lttng_ust_futex_async (op=0, val=0, timeout=0x0, uaddr2=0x0, val3=0,
uaddr=0xffffbefd7000) at ../../../src/lib/lttng-ust/futex.h:88
#3  wait_for_sessiond (sock_info=0xffffbef695e0 <local_apps>) at
lttng-ust-comm.c:1761
#4  ust_listener_thread (arg=0xffffbef695e0 <local_apps>) at
lttng-ust-comm.c:1832
#5  0x0000ffffbe9206a8 in start_thread (arg=0xffffc1bd8687) at
pthread_create.c:442
#6  0x0000ffffbe98801c in thread_start () at
../sysdeps/unix/sysv/linux/aarch64/clone.S:79

Thread 1 (Thread 0xffffbefcf460 (LWP 545)):
#0  __strlen_asimd () at ../sysdeps/aarch64/multiarch/strlen_asimd.S:96
#1  0x0000ffffbe834bd0 in lttng_ust_tp_validate_event_name
(tp=0xaaaab8f14de0
<lttng_ust_tracepoint_hello_world___my_first_tracepoint>, tp=0xaaaab8f14de0
<lttng_ust_tracepoint_hello_world___my_first_tracepoint>) at
tracepoint.c:143
#2  add_callsite (tp=0xaaaab8f14de0
<lttng_ust_tracepoint_hello_world___my_first_tracepoint>,
lib=0xaaaae74fad30) at tracepoint.c:412
#3  lib_register_callsites (lib=0xaaaae74fad30) at tracepoint.c:552
#4  lttng_ust_tracepoint_module_register (tracepoints_start=<optimized
out>, tracepoints_count=<optimized out>) at tracepoint.c:956
#5  0x0000aaaab8758204 in lttng_ust.tracepoints.ptrs_init ()
#6  0x0000ffffbe8cb30c in call_init (env=<optimized out>,
argv=0xffffc1bd8c88, argc=1) at ../csu/libc-start.c:145
#7  __libc_start_main_impl (main=0xaaaab867aabc <main>, argc=1,
argv=0xffffc1bd8c88, init=<optimized out>, fini=<optimized out>,
rtld_fini=<optimized out>, stack_end=<optimized out>) at
../csu/libc-start.c:376
#8  0x0000aaaab867a7f0 in _start () at ../sysdeps/aarch64/start.S:81

Regards,

Brian

[-- Attachment #1.2: Type: text/html, Size: 5738 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:[~2024-07-17  1:27 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
     [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 [this message]
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=CAFZh4h_pOCzpJ6ssdZ7ts3vSdJNfEtS+d+2Foi4qAY6oH0+VKw@mail.gmail.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