From: Kienan Stewart via lttng-dev <lttng-dev@lists.lttng.org>
To: Christopher Harvey <chris@cwharvey.ca>,
lttng-dev@lists.lttng.org, chris@cwharvey.ca
Subject: Re: [lttng-dev] What is DEFINE_LTTNG_UST_SIGBUS_STATE for and other beginner questions
Date: Thu, 5 Oct 2023 15:59:06 -0400 [thread overview]
Message-ID: <2d0b12a8-426f-4dbe-bde4-de6968dbd879@efficios.com> (raw)
In-Reply-To: <7619596b-4c04-47d3-91ad-da49786fcfac@app.fastmail.com>
Hi Chris,
glad that you got it figured out! I created an issue based on your
feedback. https://bugs.lttng.org/issues/1393
thanks,
kienan
On 2023-10-05 15:40, Christopher Harvey wrote:
> I got this one figured out. I used strace -fp <pid> -trace=connect on the target app to see why the connect was failing and it turns out there was a mismatch between sessiond's apps-socket paths and libust's.
>
> time to review my build environment I guess. It's very possible my docker container's path environment variables are non-standard.
>
> If I had a tiny bit of feedback to provide it would be to print out the errno and paths in the connect/bind commands in the DBG commands. I had to bust out strace to get that info. Small problem, but it could have saved me a few hours and some mailing list messages.
>
> Thank you for making this nice looking software available for free. Looking forward to playing with it some more.
>
> -Chris
_______________________________________________
lttng-dev mailing list
lttng-dev@lists.lttng.org
https://lists.lttng.org/cgi-bin/mailman/listinfo/lttng-dev
prev parent reply other threads:[~2023-10-05 19:59 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-10-04 16:56 [lttng-dev] What is DEFINE_LTTNG_UST_SIGBUS_STATE for and other beginner questions Christopher Harvey via lttng-dev
2023-10-04 19:04 ` Kienan Stewart via lttng-dev
2023-10-04 23:12 ` Christopher Harvey via lttng-dev
2023-10-05 19:40 ` Christopher Harvey via lttng-dev
2023-10-05 19:59 ` Kienan Stewart 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=2d0b12a8-426f-4dbe-bde4-de6968dbd879@efficios.com \
--to=lttng-dev@lists.lttng.org \
--cc=chris@cwharvey.ca \
--cc=kstewart@efficios.com \
/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;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).