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

External debugger #54532

Closed
antonio-petricca opened this issue Jul 18, 2018 · 5 comments
Closed

External debugger #54532

antonio-petricca opened this issue Jul 18, 2018 · 5 comments
Assignees
Labels
*caused-by-extension Issue identified to be caused by an extension

Comments

@antonio-petricca
Copy link

  • VSCode Version:

Version: 1.26.0-insider
Commit: d1272ff
Date: 2018-07-17T08:37:44.704Z
Electron: 1.7.12
Chrome: 58.0.3029.110
Node.js: 7.9.0
V8: 5.8.283.38
Architecture: x64

  • OS Version:

Distributor ID: LinuxMint
Description: Linux Mint 19 Tara
Release: 19
Codename: tara

Steps to Reproduce:

  1. Install VS Code Bash Debugger.
  2. Add to launch.json:
            "console": "externalTerminal",
            "env": {
                "TERM": "mate-terminal"
            },
  1. Run debugger

  2. Output:

TERM environment variable not set.

@weinand
Copy link
Contributor

weinand commented Jul 18, 2018

Please file this issue against the Bash debugger.

@weinand weinand added the *caused-by-extension Issue identified to be caused by an extension label Jul 18, 2018
@vscodebot
Copy link

vscodebot bot commented Jul 18, 2018

This issue is caused by an extension, please file it with the repository (or contact) the extension has linked in its overview in VS Code or the marketplace for VS Code. See also our issue reporting guidelines.

Happy Coding!

@vscodebot vscodebot bot closed this as completed Jul 18, 2018
@antonio-petricca
Copy link
Author

antonio-petricca commented Jul 18, 2018

Could you explain why you assess this?
Could you point me to a guide to configure the external terminal for the current insiders release?

Thank you again!

@weinand
Copy link
Contributor

weinand commented Jul 18, 2018

@antonio-petricca how a terminal is configured for debugging depends on the debug extension. Passing environment variables specified in a debug config to the debugger or debuggee is the responsibility of the debug extension. VS Code does neither control nor prescribe how this is done.

@antonio-petricca
Copy link
Author

Thank you for you kindly answer!

@vscodebot vscodebot bot locked and limited conversation to collaborators Sep 1, 2018
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
*caused-by-extension Issue identified to be caused by an extension
Projects
None yet
Development

No branches or pull requests

2 participants