Re: [yocto] Using lttng-ust 2.13.6 from Yocto Kirkstone and getting weird segfault saying strlen_asimd.S can't be found.

2024-07-11 Thread Brian Hutchinson
On Wed, Jul 10, 2024 at 9:53 PM Brian Hutchinson wrote: > Hi, > > I'm getting a weird segfault when I compile in a lttng-ust tracepoint into > my application. > > I'm able to run the lttng-ust hello_world example just fine on my platform > which one would think s

Re: [yocto] [lttng-dev] Using lttng-ust 2.13.6 from Yocto Kirkstone and getting weird segfault saying strlen_asimd.S can't be found.

2024-07-16 Thread Brian Hutchinson
Hi Kienan, On Thu, Jul 11, 2024 at 8:38 AM Kienan Stewart 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 coul

Re: [yocto] [lttng-dev] Using lttng-ust 2.13.6 from Yocto Kirkstone and getting weird segfault saying strlen_asimd.S can't be found.

2024-07-25 Thread Brian Hutchinson
not portable! CC app_ust_indirect_abi0_abi1-app_ust.o CC app_ust_indirect_abi0_abi1-tp.o CCLD app_ust_indirect_abi0_abi1 *** Warning: Linking the executable app_ust_indirect_abi0_abi1 against the loadable module *** libzero.so is not portable! I don't know if these are ok

Re: [yocto] [lttng-dev] Using lttng-ust 2.13.6 from Yocto Kirkstone and getting weird segfault saying strlen_asimd.S can't be found.

2024-07-30 Thread Brian Hutchinson
On Mon, Jul 29, 2024 at 3:03 PM Kienan Stewart wrote: > > Hi Brian, > > On 7/25/24 3:54 PM, Brian Hutchinson wrote: > > Hi Kienan, > > > > I'll answer your questions below, but I've got questions on what I saw > > building and installing lttng-tools (

Re: [yocto] [lttng-dev] Using lttng-ust 2.13.6 from Yocto Kirkstone and getting weird segfault saying strlen_asimd.S can't be found.

2024-07-30 Thread Brian Hutchinson
quot;make check" that I don't know if they are "good" or "bad" but could be related??? Anyway, attaching a tar of lttng-ust and lttng-tools "make check" for your enjoyment. Regards, Brian On Tue, Jul 30, 2024 at 8:40 AM Brian Hutchinson wrote: &g

Re: [yocto] [lttng-dev] Using lttng-ust 2.13.6 from Yocto Kirkstone and getting weird segfault saying strlen_asimd.S can't be found.

2024-07-30 Thread Brian Hutchinson
e=gnu --enable-linker-build-id --with-ppl=no --with-cloog=no --enable-checking=release --enable-cheaders=c_global --without-isl --with-build-sysroot=/ --disable-static --enable-nls - -with-glibc-version=2.28 --enable-initfini-array --enable-__cxa_atexit Thread model: posix Regards, Brian On Tue,

Re: [yocto] [lttng-dev] Using lttng-ust 2.13.6 from Yocto Kirkstone and getting weird segfault saying strlen_asimd.S can't be found.

2024-08-21 Thread Brian Hutchinson
hello.o hello-tp.o -llttng-ust -ldl I know ... you're gonna say don't do that, but this is embedded and millions of lines of code so it is what it is. Regards, Brian On Tue, Jul 30, 2024 at 11:58 AM Kienan Stewart wrote: > > Hi Brian, > > On 7/30/24 11:54 AM, Brian Hutchinso

Re: [lttng-dev] Using lttng 2.11 and UST doesn't appear to work - getting empty trace files

2023-04-24 Thread Brian Hutchinson via lttng-dev
So instructions for tracef just say to link in lttng-ust, not dl, I didn't use liblttng-ust.a so maybe I misspoke. https://lttng.org/docs/v2.11/#doc-tracef ... so that's what I did. When I compile in a tracepoint with trace provider, I link in lttng-ust and dl. I'm assuming you can mix both tra

Re: [lttng-dev] Using lttng 2.11 and UST doesn't appear to work - getting empty trace files

2023-04-25 Thread Brian Hutchinson via lttng-dev
at ../../../../lttng-tools-2.11.5/src/bin/lttng-sessiond/client.c:659) Not quite sure what to do about that. Regards, Brian On Tue, Apr 25, 2023 at 12:56 AM Brian Hutchinson wrote: > So instructions for tracef just say to link in lttng-ust, not dl, I didn't > use liblttng-ust.a

[lttng-dev] I'm still getting empty ust traces using tracef

2023-05-11 Thread Brian Hutchinson via lttng-dev
Hi, I posted a while ago (thread - Using lttng 2.11 and UST doesn't appear to work - getting empty trace files) about this problem I'm having with getting empty trace logs. I've since upgraded to lttng v2.13 and while I can do a simple hello world program with tracef and get events in the log fil

Re: [lttng-dev] I'm still getting empty ust traces using tracef

2023-05-11 Thread Brian Hutchinson via lttng-dev
... more background. I've always used ltt in the kernel so I don't have much experience with the user side of it and especially multi-threaded, multi-core so I'm probably missing some fundamental concepts that I need to understand. Regards, Brian On Thu, May 11, 2023 at

Re: [lttng-dev] I'm still getting empty ust traces using tracef

2023-05-11 Thread Brian Hutchinson via lttng-dev
Hi Mathieu, On Thu, May 11, 2023 at 2:12 PM Mathieu Desnoyers wrote: > > On 2023-05-11 12:36, Brian Hutchinson via lttng-dev wrote: > > ... more background. I've always used ltt in the kernel so I don't > > have much experience with the user side of it and especial

Re: [lttng-dev] I'm still getting empty ust traces using tracef

2023-05-11 Thread Brian Hutchinson via lttng-dev
On Thu, May 11, 2023 at 2:14 PM Michael Jeanson wrote: > > On 2023-05-11 12:36, Brian Hutchinson via lttng-dev wrote: > > ... more background. I've always used ltt in the kernel so I don't > > have much experience with the user side of it and especially > >

Re: [lttng-dev] I'm still getting empty ust traces using tracef

2023-05-11 Thread Brian Hutchinson via lttng-dev
On Thu, May 11, 2023 at 12:36 PM Brian Hutchinson wrote: > > ... more background. I've always used ltt in the kernel so I don't > have much experience with the user side of it and especially > multi-threaded, multi-core so I'm probably missing some fundamenta

Re: [lttng-dev] I'm still getting empty ust traces using tracef

2023-05-12 Thread Brian Hutchinson via lttng-dev
Hi Mathieu, On Fri, May 12, 2023 at 9:33 AM Mathieu Desnoyers wrote: > > On 2023-05-12 00:10, Brian Hutchinson wrote: > > Hmm, I missed this earlier somehow. > > > > So, I'm not the greatest at updating OE and Yocto recipes. I'm > > currently using this

[lttng-dev] Trying to understand use of lttng enable-event --kernel --userspace-probe=

2023-05-16 Thread Brian Hutchinson via lttng-dev
Hi, I'm trying to figure out how to use uprobes with lttng. I can't use a normal uprobe for a line number just using the address I want to probe obtained from objdump? As in: echo 'p /usr/local/bin/my_app:0x2c3a8' >> /sys/kernel/debug/tracing/uprobe_events ... which isn't a function entry, it'

Re: [lttng-dev] Trying to understand use of lttng enable-event --kernel --userspace-probe=

2023-05-17 Thread Brian Hutchinson via lttng-dev
On Wed, May 17, 2023 at 12:08 PM Mathieu Desnoyers wrote: > > On 2023-05-16 22:11, Brian Hutchinson via lttng-dev wrote: > > Hi, > > > > I'm trying to figure out how to use uprobes with lttng. > > > > I can't use a normal uprobe for a line num

Re: [lttng-dev] Trying to understand use of lttng enable-event --kernel --userspace-probe=

2023-05-18 Thread Brian Hutchinson via lttng-dev
On Wed, May 17, 2023 at 12:08 PM Mathieu Desnoyers wrote: > > On 2023-05-16 22:11, Brian Hutchinson via lttng-dev wrote: > > Hi, > > > > I'm trying to figure out how to use uprobes with lttng. > > > > I can't use a normal uprobe for a line num

Re: [lttng-dev] Trying to understand use of lttng enable-event --kernel --userspace-probe=

2023-05-18 Thread Brian Hutchinson via lttng-dev
On Thu, May 18, 2023 at 9:17 AM Brian Hutchinson wrote: > > On Wed, May 17, 2023 at 12:08 PM Mathieu Desnoyers > wrote: > > > > On 2023-05-16 22:11, Brian Hutchinson via lttng-dev wrote: > > > Hi, > > > > > > I'm trying to figure out how

Re: [lttng-dev] Trying to understand use of lttng enable-event --kernel --userspace-probe=

2023-05-18 Thread Brian Hutchinson via lttng-dev
On Thu, May 18, 2023 at 10:45 AM Mathieu Desnoyers wrote: > > On 2023-05-18 10:10, Brian Hutchinson wrote: > [...] > > I updated my hello world to have a function I'd like to use the > > --userspace-probe method on with the very original name of > > &#

Re: [lttng-dev] Trying to understand use of lttng enable-event --kernel --userspace-probe=

2023-05-18 Thread Brian Hutchinson via lttng-dev
On Thu, May 18, 2023 at 11:00 AM Brian Hutchinson wrote: > > On Thu, May 18, 2023 at 10:45 AM Mathieu Desnoyers > wrote: > > > > On 2023-05-18 10:10, Brian Hutchinson wrote: > > [...] > > > I updated my hello world to have a function I'd like to use the &

Re: [lttng-dev] Trying to understand use of lttng enable-event --kernel --userspace-probe=

2023-05-18 Thread Brian Hutchinson via lttng-dev
On Thu, May 18, 2023 at 3:03 PM Mathieu Desnoyers wrote: > > On 2023-05-18 14:58, Brian Hutchinson wrote: > > On Thu, May 18, 2023 at 11:00 AM Brian Hutchinson > > wrote: > >> > >> On Thu, May 18, 2023 at 10:45 AM Mathieu Desnoyers > >> wrote: >

Re: [lttng-dev] Trying to understand use of lttng enable-event --kernel --userspace-probe=

2023-05-18 Thread Brian Hutchinson via lttng-dev
On Thu, May 18, 2023 at 3:07 PM Brian Hutchinson wrote: > > On Thu, May 18, 2023 at 3:03 PM Mathieu Desnoyers > wrote: > > > > On 2023-05-18 14:58, Brian Hutchinson wrote: > > > On Thu, May 18, 2023 at 11:00 AM Brian Hutchinson > > > wrote: > &g

Re: [lttng-dev] Trying to understand use of lttng enable-event --kernel --userspace-probe=

2023-05-18 Thread Brian Hutchinson via lttng-dev
On Thu, May 18, 2023 at 3:16 PM Mathieu Desnoyers wrote: > > On 2023-05-18 15:07, Brian Hutchinson wrote: > > [...] > > >> > >> If you attach to an ELF symbol (function), then there is no USDT in > >> play, so it should not be related to the issue you

Re: [lttng-dev] Trying to understand use of lttng enable-event --kernel --userspace-probe=

2023-05-18 Thread Brian Hutchinson via lttng-dev
On Thu, May 18, 2023 at 3:24 PM Mathieu Desnoyers wrote: > > On 2023-05-18 15:20, Brian Hutchinson wrote: > > On Thu, May 18, 2023 at 3:07 PM Brian Hutchinson > > wrote: > >> > >> On Thu, May 18, 2023 at 3:03 PM Mathieu Desnoyers > >> wrote: >

Re: [lttng-dev] I'm still getting empty ust traces using tracef

2023-06-20 Thread Brian Hutchinson via lttng-dev
On Thu, May 11, 2023 at 2:14 PM Mathieu Desnoyers wrote: > > On 2023-05-11 14:13, Mathieu Desnoyers via lttng-dev wrote: > > On 2023-05-11 12:36, Brian Hutchinson via lttng-dev wrote: > >> ... more background. I've always used ltt in the kernel so I don't > >

Re: [lttng-dev] I'm still getting empty ust traces using tracef

2023-06-21 Thread Brian Hutchinson via lttng-dev
On Wed, Jun 21, 2023 at 4:21 PM Mathieu Desnoyers wrote: > > On 6/20/23 18:02, Brian Hutchinson wrote: > > On Thu, May 11, 2023 at 2:14 PM Mathieu Desnoyers > > wrote: > >> > >> On 2023-05-11 14:13, Mathieu Desnoyers via lttng-dev wrote: > >>> On

Re: [lttng-dev] I'm still getting empty ust traces using tracef

2023-06-28 Thread Brian Hutchinson via lttng-dev
On Wed, Jun 21, 2023 at 6:02 PM Brian Hutchinson wrote: > > On Wed, Jun 21, 2023 at 4:21 PM Mathieu Desnoyers > wrote: > > > > On 6/20/23 18:02, Brian Hutchinson wrote: > > > On Thu, May 11, 2023 at 2:14 PM Mathieu Desnoyers > > > wrote: > > >>

[lttng-dev] Using lttng-ust 2.13.6 from Yocto Kirkstone and getting weird segfault saying strlen_asimd.S can't be found.

2024-07-10 Thread Brian Hutchinson via lttng-dev
Hi, I'm getting a weird segfault when I compile in a lttng-ust tracepoint into my application. I'm able to run the lttng-ust hello_world example just fine on my platform which one would think should prove everything out, but when I use the exact same hello world trace provider and link it into my

Re: [lttng-dev] Using lttng-ust 2.13.6 from Yocto Kirkstone and getting weird segfault saying strlen_asimd.S can't be found.

2024-07-17 Thread Brian Hutchinson via lttng-dev
./my-app Typical use cases include closing all the file descriptors after fork(2) <https://man7.org/linux/man-pages/man2/fork.2.html> or rfork(2) <http://www.freebsd.org/cgi/man.cgi?query=rfork&sektion=2&manpath=FreeBSD+4.10-RELEASE> and buggy applications doing “double closes”. Thanks