microsoft / vscode

Visual Studio Code
https://code.visualstudio.com
MIT License
162.65k stars 28.68k forks source link

Terminal #213748

Closed SuRochaa closed 3 months ago

SuRochaa commented 3 months ago

Type: Bug

O terminal não está rodando o programa. Aparece a seguinte frase: "

O processo de terminal falhou ao iniciar: A native exception occurred during launch (posix_spawnp failed.)".

VS Code version: Code 1.88.1 (Universal) (e170252f762678dec6ca2cc69aba1570769a5d39, 2024-04-10T17:42:52.765Z) OS version: Darwin arm64 22.6.0 Modes:

System Info |Item|Value| |---|---| |CPUs|Apple M1 (8 x 24)| |GPU Status|2d_canvas: enabled
canvas_oop_rasterization: enabled_on
direct_rendering_display_compositor: disabled_off_ok
gpu_compositing: enabled
multiple_raster_threads: enabled_on
opengl: enabled_on
rasterization: enabled
raw_draw: disabled_off_ok
skia_graphite: disabled_off
video_decode: enabled
video_encode: enabled
webgl: enabled
webgl2: enabled
webgpu: enabled| |Load (avg)|1, 2, 2| |Memory (System)|8.00GB (0.07GB free)| |Process Argv|--crash-reporter-id 5f37e707-0b86-4c70-ade5-e1c14bb1a43e| |Screen Reader|no| |VM|0%|
Extensions (38) Extension|Author (truncated)|Version ---|---|--- codesnap|adp|1.3.4 vscode-caniuse|aka|0.5.4 snippets-plotly|ana|2.0.4 icons-carbon|ant|0.2.6 bootstrap-5-snippets|bab|0.1.1 macos-modern-theme|dav|2.3.19 vscode-html-css|ecm|2.0.9 ionic-preview|ion|0.0.20 rainbow-csv|mec|3.12.0 emoji-icons|mig|1.6.1 vscode-language-pack-pt-BR|MS-|1.88.2024041009 debugpy|ms-|2024.6.0 python|ms-|2024.4.1 vscode-pylance|ms-|2024.5.1 jupyter|ms-|2024.3.1 jupyter-keymap|ms-|1.1.2 jupyter-renderers|ms-|1.0.17 vscode-jupyter-cell-tags|ms-|0.1.9 vscode-jupyter-slideshow|ms-|0.1.6 w-snippets|ngv|1.0.5 vscode-numpy-viewer|Per|0.1.8 developer-theme-dark|Raj|5.0.0 java|red|1.30.0 LiveServer|rit|5.7.9 synthwave-vscode|Rob|0.1.15 flet-control-wrap|sob|0.0.2 ayu|tea|1.0.5 pdf|tom|1.2.2 intellicode-api-usage-examples|Vis|0.2.8 vscodeintellicode|Vis|1.3.1 vscode-java-debug|vsc|0.57.0 vscode-java-dependency|vsc|0.23.6 vscode-java-pack|vsc|0.26.0 vscode-java-test|vsc|0.41.1 vscode-maven|vsc|0.44.0 html-snippets|wsc|1.0.6 theme-demo|xin|0.0.1 html-css-class-completion|Zig|1.20.0 (13 theme extensions excluded)
A/B Experiments ``` vsliv368:30146709 vspor879:30202332 vspor708:30202333 vspor363:30204092 vscod805:30301674 binariesv615:30325510 vsaa593cf:30376535 py29gd2263:31024239 c4g48928:30535728 azure-dev_surveyone:30548225 962ge761:30959799 pythongtdpath:30769146 pythonidxpt:30866567 pythonnoceb:30805159 asynctok:30898717 pythontestfixt:30902429 pythonregdiag2:30936856 pythonmypyd1:30879173 pythoncet0:30885854 2e7ec940:31000449 pythontbext0:30879054 dsvsc016:30899300 dsvsc017:30899301 dsvsc018:30899302 cppperfnew:31000557 dsvsc020:30976470 pythonait:31006305 dsvsc021:30996838 f3je6385:31013174 a69g1124:31058053 dvdeprecation:31061160 pythonprt:31056678 dwnewjupyter:31046869 26j00206:31048877 ```
VSCodeTriageBot commented 3 months ago

Thanks for creating this issue! It looks like you may be using an old version of VS Code, the latest stable release is 1.89.1. Please try upgrading to the latest version and checking whether this issue remains.

Happy Coding!

meganrogge commented 3 months ago

This error typically occurs when the system is unable to find the executable you're trying to run. Here are a few things you can try to resolve this issue:

Check the path to the executable: Make sure the path to the executable in your launch configuration is correct. If the executable is in your system's PATH, you should be able to just specify the executable's name, otherwise you'll need to specify the full path.

Check the executable permissions: Make sure the executable has the correct permissions. You can check this by running ls -l in the terminal. If the executable doesn't have execute permissions, you can add them by running chmod +x .

Reinstall the executable: If the executable is part of a larger software package, it might help to reinstall that package.

Check your system's PATH: If the executable is supposed to be in your system's PATH, make sure your PATH is set up correctly. You can check your PATH by running echo $PATH in the terminal.