From: Nick Alcock <nix@esperi.org.uk>
To: Kris Van Hees <kris.van.hees@oracle.com>
Cc: dtrace@lists.linux.dev, dtrace-devel@oss.oracle.com
Subject: Re: [PATCH 11/20] libdtrace: cache missing kernel CTF archives until paths change
Date: Fri, 06 Nov 2026 13:00:45 +0000 [thread overview]
Message-ID: <875wyat8qq.fsf@esperi.org.uk> (raw)
In-Reply-To: <24b4b0f9f1f1b21146f37d5f08386734@oracle.com>
On 30 Oct 2026, Kris Van Hees said:
> ---
> libdtrace/dt_impl.h | 1 +
> libdtrace/dt_module.c | 16 +++++++++++--
> libdtrace/dt_options.c | 3 +++
> test/triggers/Build | 1 +
> test/triggers/shared-ctf.c | 49 ++++++++++++++++++++++++++++++++++++++
> 5 files changed, 68 insertions(+), 2 deletions(-)
... why on earth would they ever be missing? Surely fixing that instead
is a good idea? (Or is this something to do with chroots and containers
and the CTFA being in a filesystem path whose meaning will change in the
middle of execution or something?)
--
NULL && (void)
next prev parent reply other threads:[~2026-11-06 13:00 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-10-30 19:36 [PATCH 11/20] libdtrace: cache missing kernel CTF archives until paths change Kris Van Hees
2026-11-06 13:00 ` Nick Alcock [this message]
2026-11-06 21:24 ` Kris Van Hees
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=875wyat8qq.fsf@esperi.org.uk \
--to=nix@esperi.org.uk \
--cc=dtrace-devel@oss.oracle.com \
--cc=dtrace@lists.linux.dev \
--cc=kris.van.hees@oracle.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