microsoft / microsoft/vscode-python-debugger

$PATH ordering is wrong when running with Python debugger.

Open
#258 3 comments 0 reactions 1 assignee View on GitHub

@karthiknadig is already working on this.

Since Aug 8, 2024.

bug needs PR
Dominant language
TypeScript
Stars
180
Forks
126
Avg merge
2d 3h
Merged PRs (30d)
3

Description

Issue Type: Bug

  1. Open a Python file.
  2. Press Ctrl-F5 to run a Python file.
  3. The Python file uses another executable (specifically, clang).
  4. My code fails because the $PATH order is different than it should be and as a result the clang call is using the wrong clang installation and fails..

See the screenshots for how the which clang output differs between the debugger terminal and the standard terminal. The origin of this problem is that the $PATH environment variable is in the wrong order in the debugger terminal.

164948222-8b8b9120-302e-42e4-b50c-8a1c9afeca3a

Extension version: 2022.4.1
VS Code version: Code 1.66.2 (Universal) (dfd34e8260c270da74b5c2d86d61aee4b6d56977, 2022-04-11T07:49:20.994Z)
OS version: Darwin arm64 21.4.0
Restricted Mode: No

System Info
Item Value
CPUs Apple M1 Max (10 x 24)
GPU Status 2d_canvas: enabled
canvas_oop_rasterization: disabled_off
direct_rendering_display_compositor: disabled_off_ok
gpu_compositing: enabled
metal: disabled_off
multiple_raster_threads: enabled_on
oop_rasterization: enabled
opengl: enabled_on
rasterization: enabled
raw_draw: disabled_off_ok
skia_renderer: enabled_on
video_decode: enabled
video_encode: enabled
webgl: enabled
webgl2: enabled
Load (avg) 5, 4, 3
Memory (System) 64.00GB (23.60GB free)
Process Argv --crash-reporter-id b532f079-f941-47c0-ab2f-f74d9a137557
Screen Reader no
VM 0%

Contributor guide

Open the contributing guide

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

Assessment

This issue has not been assessed yet.

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.