From: Masami Hiramatsu (Google) <mhiramat@kernel.org>
To: Yuxuan Shui <yshuiv7@gmail.com>
Cc: linux-trace-kernel@vger.kernel.org,
Steven Rostedt <rostedt@goodmis.org>,
Masami Hiramatsu <mhiramat@kernel.org>,
Mathieu Desnoyers <mathieu.desnoyers@efficios.com>,
open list <linux-kernel@vger.kernel.org>
Subject: Re: uprobe_events can't accept paths that contain spaces
Date: Mon, 25 Nov 2024 15:43:56 +0900 [thread overview]
Message-ID: <20241125154356.1e44f3c5775bb30269ed28a5@kernel.org> (raw)
In-Reply-To: <CAGqt0zxtKboY1PWRN4kCF3uTeiH9ZJtj280ARvGWeNtR_ik0eQ@mail.gmail.com>
On Fri, 22 Nov 2024 00:42:51 +0000
Yuxuan Shui <yshuiv7@gmail.com> wrote:
> Hi,
>
> I hit this problem accidentally when one of the shared libraries I was
> looking at is located in a directory with spaces in its name. `perf
> probe` reported "Failed to write event: Invalid argument".
Oops, yes, it is limited by implementation.
>
> If I understand the code correctly, strings written into uprobe_events
> are strictly splitted at whitespaces (by `argv_split`).
Right!
> This seems
> like an unfortunate restriction. If I submit a patch to introduce
> support for either quotes (") or escapes (\), will that be considered?
Yeah, that enhancement is welcome! You can add such function in
trace_probe.c and use it instead of argv_split.
>
> (For context I am running something that expects its libraries to be
> located at fixed paths, so moving them to a different path would be
> awkward at best.)
Thanks,
>
> Thanks.
>
> --
>
> Regards
> Yuxuan Shui
--
Masami Hiramatsu (Google) <mhiramat@kernel.org>
prev parent reply other threads:[~2024-11-25 6:43 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-11-22 0:42 Yuxuan Shui
2024-11-25 6:43 ` Masami Hiramatsu [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=20241125154356.1e44f3c5775bb30269ed28a5@kernel.org \
--to=mhiramat@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-trace-kernel@vger.kernel.org \
--cc=mathieu.desnoyers@efficios.com \
--cc=rostedt@goodmis.org \
--cc=yshuiv7@gmail.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
all inboxes | Powered by JetHome®