GraalVM node: --agent option seems unknown

raffaello.giulietti at supsi.ch raffaello.giulietti at supsi.ch
Wed May 2 18:27:43 UTC 2018


Hi Christian,

indeed, I can confirm that it now works.

Thanks
Raffaello




On 2018-05-02 20:09, Christian Humer wrote:
> Hi Raffaello,
> 
> Thanks a lot for the report. Unfortunately in RC1 none of the tools made
> it into the native-image for our node executable due to some glitch in
> our build system.
> 
> The workaround is to also pass in the --jvm option. For example: node
> --agent --jvm.
> 
> This is fixed with RC2 that is scheduled for start of June.
> 
> - Christian Humer
> 
> 
> 
> 
> 
> On Wed, May 2, 2018 at 7:19 PM <raffaello.giulietti at supsi.ch
> <mailto:raffaello.giulietti at supsi.ch>> wrote:
> 
>     Hi,
> 
>     I'm not sure if this is the right list for my question below. If not,
>     sorry for that.
> 
>     I'm trying to follow the GraalVM example with the Monitoring Agent
>     http://www.graalvm.org/docs/reference-manual/tools/#monitoring-agent
>     but cannot pass the --agent option to node: it seems unknown for some
>     reason.
> 
>     I'm with the Enterprise edition of GraalVM (1.0.0-rc1) and on Linux.
>     Yes, I checked that node is GraalVM's own node (v8.9.4)
> 
> 
>     Greetings
>     Raffaello
> 



More information about the graal-dev mailing list