enso-org/enso
1
1
Fork 0
mirror of https://github.com/enso-org/enso.git synced 2024-11-27 02:55:06 +03:00
Code Issues Projects Releases Wiki Activity
2e7d71d459
enso/docs/debugger/chrome-devtools.md
Pavel Marek 8e49255d92
Invoke all Enso benchmarks via JMH (#7101) 
# Important Notes
#### The Plot

- there used to be two kinds of benchmarks: in Java and in Enso
- those in Java got quite a good treatment
- there even are results updated daily: https://enso-org.github.io/engine-benchmark-results/
- the benchmarks written in Enso used to be 2nd class citizen

#### The Revelation
This PR has the potential to fix it all!
- It designs new [Bench API](88fd6fb988) ready for non-batch execution
- It allows for _single benchmark in a dedicated JVM_ execution
- It provides a simple way to wrap such an Enso benchmark as a Java benchmark
- thus the results of Enso and Java benchmarks are [now unified](https://github.com/enso-org/enso/pull/7101#discussion_r1257504440)

Long live _single benchmarking infrastructure for Java and Enso_!
2023-08-07 12:39:01 +00:00

1.8 KiB
Raw Blame History

Chrome Developer Tools Debugger

As a well written citizen of the GraalVM project the Enso language can be used with existing tools available for the overall platform. One of them is Chrome Debugger and Enso language is fully integrated with it. Launch the bin/enso executable with additional --inspect option and debug your Enso programs in Chrome Developer Tools.

enso$ ./built-distribution/enso-engine-*/enso-*/bin/enso --inspect --run ./test/Tests/src/Data/Numbers_Spec.enso
Debugger listening on ws://127.0.0.1:9229/Wugyrg9
For help, see: https://www.graalvm.org/tools/chrome-debugger
E.g. in Chrome open: devtools://devtools/bundled/js_app.html?ws=127.0.0.1:9229/Wugyrg9

copy the printed URL into chrome browser and you should see:

Chrome Debugger

Step in, step over, set breakpoints, watch values of the variables as well as evaluate arbitrary expressions in the console. Note that as of December 2022, with GraalVM 22.3.0, there is a well-known bug in Truffle that causes NullPointerException when a host object gets into the chrome inspector. There is a workaround for that, but it may not work in certain situations. Therefore, if you encounter NullPointerException thrown from

at org.graalvm.truffle/com.oracle.truffle.polyglot.PolyglotContextImpl.getContext(PolyglotContextImpl.java:685)

simply ignore it. It will be handled within the debugger and should not affect the rest of the environment.

Tips and tricks

  • Use env JAVA_OPTS=-Dpolyglot.inspect.Path=enso_debug to set the chrome to use a fixed URL. In this case the URL is devtools://devtools/bundled/js_app.html?ws=127.0.0.1:9229/enso_debug