From: Nick Alcock <nick.alcock@oracle.com>
To: Kris Van Hees <kris.van.hees@oracle.com>
Cc: Eugene Loh <eugene.loh@oracle.com>,
Nick Alcock <nick.alcock@oracle.com>, <dtrace@lists.linux.dev>,
<dtrace-devel@oss.oracle.com>
Subject: Re: [DTrace-devel] [PATCH v2] dtprobed: use /proc/$pid/map_files, not the filename of the mapping
Date: Thu, 12 Feb 2026 18:56:12 +0000 [thread overview]
Message-ID: <871pipokoj.fsf@esperi.org.uk> (raw)
In-Reply-To: <aY4hQajn7use525y@oracle.com> (Kris Van Hees's message of "Thu, 12 Feb 2026 13:51:45 -0500")
On 12 Feb 2026, Kris Van Hees outgrape:
> On Thu, Feb 12, 2026 at 01:49:54PM -0500, Eugene Loh wrote:
>> On 2/12/26 13:43, Kris Van Hees wrote:
>>
>> > I believe the following on top of the original patch should resolve this:
>> >
>> > diff --git a/dtprobed/dtprobed.c b/dtprobed/dtprobed.c
>> > index 9a692805..34349deb 100644
>> > --- a/dtprobed/dtprobed.c
>> > +++ b/dtprobed/dtprobed.c
>> > @@ -487,16 +487,17 @@ handle_usdt_notes(pid_t pid, uintptr_t addr)
>> > fuse_log(FUSE_LOG_ERR, "%i: dtprobed: cannot look up mapping (process dead?)\n",
>> > pid);
>> > goto out;
>> > - } else if ((fn = Pmap_mapfile_name(P, mapp)) == NULL) {
>> > + } else if (prf->prf_mapname == NULL ||
>> > + (fn = Pmap_mapfile_name(P, mapp)) == NULL) {
>> > fuse_log(FUSE_LOG_ERR, "%i: dtprobed: cannot look up mapname (process dead?)\n",
>> > pid);
>> > goto out;
>> > }
>> > - mod = strrchr(fn, '/');
>> > + mod = strrchr(prf->prf_mapname, '/');
>> > if (mod)
>> > mod++;
>> > else
>> > - mod = fn;
>>
>> Is that a '-' on the last line?
>
> Yes, but it is missing the last line (sorry about that):
>
> + mod = prf->prf_mapname;
Given that...
Reviewed-by: Nick Alcock <nick.alcock@oracle.com>
I have *no idea* how this worked when I tested it. The whole testsuite
passed...
prev parent reply other threads:[~2026-02-12 18:56 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-12-02 23:04 [PATCH] dtprobed: use /proc/$pid/map_files, not the filename of the mapping Nick Alcock
2025-12-04 6:18 ` Eugene Loh
2026-01-20 16:19 ` Nick Alcock
2026-01-20 16:20 ` [PATCH v2] " Nick Alcock
2026-01-20 19:24 ` [DTrace-devel] " Eugene Loh
2026-02-12 18:13 ` Eugene Loh
2026-02-12 18:18 ` Nick Alcock
2026-02-12 18:28 ` Kris Van Hees
2026-02-12 18:37 ` Kris Van Hees
2026-02-12 18:43 ` Kris Van Hees
2026-02-12 18:49 ` Eugene Loh
2026-02-12 18:51 ` Kris Van Hees
2026-02-12 18:56 ` Nick Alcock [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=871pipokoj.fsf@esperi.org.uk \
--to=nick.alcock@oracle.com \
--cc=dtrace-devel@oss.oracle.com \
--cc=dtrace@lists.linux.dev \
--cc=eugene.loh@oracle.com \
--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