<html><head><meta http-equiv="content-type" content="text/html; charset=utf-8"></head><body style="overflow-wrap: break-word; -webkit-nbsp-mode: space; line-break: after-white-space;">Hi Dries,<div><br></div><div>Have you tried escaping the spaces to that the shell doesn’t split the value?</div><div><br></div><div>Kind regards,</div><div>Kirk</div><div><br id="lineBreakAtBeginningOfMessage"><div><br><blockquote type="cite"><div>On Aug 13, 2025, at 7:59 PM, Dries Samyn <mail@dries.net> wrote:</div><br class="Apple-interchange-newline"><div><div dir="ltr"><div dir="ltr"><div>I'm not sure this is considered a bug as it matches the documented behaviour, but I can't think of a clean workaround if it is.</div><div><br></div><div>I
believe arguments passed into the -jvmArgs option are space delimited.
However, this is problematic when those arguments include spaces as part
of the value.</div><div>For example, I am trying to create a
custom profiler for YourKit integration, but the YourKit agent, by
default, has spaces in its path on MacOs, which means trying to pass it
in the jvmArgs option is problematic.</div><div><br></div><div>I have created a reproduction of the issue and explanation here: <a href="https://github.com/driessamyn/jmh-spaces-bug-reproduction" target="_blank">https://github.com/driessamyn/<span class="gmail-il">jmh</span>-spaces-bug-reproduction</a></div><div><br></div><div>Looking forward to hearing thoughts on this.</div><font color="#888888"><div><br></div><div>Dries.</div></font></div><br></div>
</div></blockquote></div><br></div></body></html>