enso-org/enso
1
1
Fork 0
mirror of https://github.com/enso-org/enso.git synced 2024-12-30 04:03:17 +03:00
Code Issues Projects Releases Wiki Activity
190029996c
enso/docs/debugger/README.md

Ignoring revisions in .git-blame-ignore-revs. Click here to bypass and see the normal blame view.

22 lines
664 B
Markdown
Raw Normal View History

Binary Protocol for the Debugger (#796)
2020-06-05 11:48:16 +03:00
---
layout: section-summary
title: Debugger
category: debugger
tags: [debugger, repl, readme]
order: 0
---
Debug Enso language in ChromeDev tools with --inspect option (#3432) Finally this pull request proposes `--inspect` option to allow [debugging of `.enso`](https://github.com/enso-org/enso/blob/e948f2535f71249daed647181324746613081d29/docs/debugger/README.md) in Chrome Developer Tools: ```bash enso$ ./built-distribution/enso-engine-0.0.0-dev-linux-amd64/enso-0.0.0-dev/bin/enso --inspect --run ./test/Tests/src/Data/Numbers_Spec.enso Debugger listening on ws://127.0.0.1:9229/Wugyrg9Nm4OUL9YhzdcElmLft71ayZW3LMUPCdPyNAY 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/Wugyrg9Nm4OUL9YhzdcElmLft71ayZW3LMUPCdPyNAY ``` copy the printed URL into chrome browser and you should see: ![obrazek](https://user-images.githubusercontent.com/26887752/167235327-8ad15fb2-96d4-4a0c-9e31-ed67ab46578b.png) One can also debug the `.enso` files in NetBeans or [VS Code with Apache Language Server extension](https://cwiki.apache.org/confluence/display/NETBEANS/Apache+NetBeans+Extension+for+Visual+Studio+Code) just pass in special JVM arguments: ```bash enso$ JAVA_OPTS=-agentlib:jdwp=transport=dt_socket,server=y,address=8000 ./built-distribution/enso-engine-0.0.0-dev-linux-amd64/enso-0.0.0-dev/bin/enso --run ./test/Tests/src/Data/Numbers_Spec.enso Listening for transport dt_socket at address: 8000 ``` and then _Debug/Attach Debugger_. Once connected choose the _Toggle Pause in GraalVM Script_ button in the toolbar (the "G" button): ![obrazek](https://user-images.githubusercontent.com/26887752/167235598-98266c7e-beb5-406b-adc6-8167b3d1b453.png) and your execution shall stop on the next `.enso` line of code. This mode allows to debug both - the Enso code as well as Java code. Originally started as an attempt to write test in Java: * test written in Java * support for JUnit in `build.sbt` * compile Java with `-g` - so it can be debugged * Implementation of `StatementNode` - only gets created when `materialize` request gets to `BlockNode`
2022-05-10 11:55:08 +03:00
# Enso Debugger
Add a markdown style guide (#1022)
2020-07-21 15:59:40 +03:00
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](https://github.com/enso-org/enso/pull/7101/commits/88fd6fb9888d939c2d9745a7397f6e87dec4fa4d) 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 15:39:01 +03:00
This folder contains all documentation pertaining to the debugging facilities
used by Enso, broken up as follows:
- [**The Enso Debugger Protocol:**](./protocol.md) The protocol for the REPL
Debugger.
- [**Chrome devtools debugger:**](./chrome-devtools.md) A guide how to debug
Enso code using Chrome devtools.
Add Chrome devtools and DAP tools for debugging (#8344) Adds chrome-inspector tool and Debug Adapter protocol tool for debugging Enso. # Important Notes The chrome devtools seems to be broken (tracked in https://github.com/oracle/graal/issues/7636). Even `graalpy --inspect ...` fails (Chrome devtools freezes after connecting to the server). This PR adds Debug adapter protocol tool for debugging as a workaround for chrome inspector. There is docs in [dap.md](https://github.com/enso-org/enso/pull/8344/files#diff-421574b50574cfe546e86d4b3d32d79b8b2087f2fe204f68e5cf2693af43bbe1)
2023-11-22 20:18:41 +03:00
- [**Debug adapter protocol:**](./dap.md) A guide how to debug Enso code using
VSCode.
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](https://github.com/enso-org/enso/pull/7101/commits/88fd6fb9888d939c2d9745a7397f6e87dec4fa4d) 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 15:39:01 +03:00
- [**Debugging Engine (Runtime) only Java code:**](./runtime-debugging.md) A
Unifying debugging information (#8370)
2023-11-27 11:37:51 +03:00
guide how to debug Enso code & the internal Java code.
Reference in New Issue Copy Permalink