Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Is the debugging feature working? #458

Closed
jradxl opened this issue Jun 25, 2021 · 2 comments
Closed

Is the debugging feature working? #458

jradxl opened this issue Jun 25, 2021 · 2 comments
Labels
duplicate This issue or pull request already exists

Comments

@jradxl
Copy link

jradxl commented Jun 25, 2021

test

Describe the bug
Use of Debugging does not work as per documentation, but I can get it to work as described below.
Ubuntu 21.04 (fully up to date, and reproduced in a newly installed Virtualbox instance)
vscode via deb package, 1.57.1
deno 1.11.2
plugin 3.6.1

To Reproduce
$cat main.ts
console.log("Hello, World!");
console.log("Hello, World!");
Deno.exit(); //<<< Needed to ensure the debugger does close correctly if/when a successful debug session is achieved.

  1. Without launch.json (the Python Plugin works like this)
    Using debug menu, using the Blue Run and Debug button, with and without breakpoint
    Generally the debugger hangs and I get the dialog, Error processing Launch ....

  2. With launch,json
    A. No output unless a
    "outputCapture": "std"
    or
    "console": "integratedTerminal"
    is added

B: No breakpoint is hit if using
--inspect

C: Debugging only works if
--inspect-brk
is used, but of course, initial stop is on first line of code.

If I am doing something wrong, I don't know what it is!

Expected behavior
To work easily without launch.json, or with a correct launch.json automatically added using --inspect

Versions
Ubuntu 21.04 (fully up to date, and reproduced in a newly installed Virtualbox instance)
vscode via deb package, 1.57.1
deno 1.11.2
plugin 3.6.1

@zandaqo
Copy link
Contributor

zandaqo commented Jun 29, 2021

The exact same situation since last May as I mentioned in #384, also went with --inspect-brk in the meantime as a workaround.

@kitsonk kitsonk added the duplicate This issue or pull request already exists label Jul 19, 2021
@kitsonk
Copy link
Contributor

kitsonk commented Jul 19, 2021

Duplicate of #384

@kitsonk kitsonk marked this as a duplicate of #384 Jul 19, 2021
@kitsonk kitsonk closed this as completed Jul 19, 2021
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
duplicate This issue or pull request already exists
Projects
None yet
Development

No branches or pull requests

3 participants