microsoft / microsoft/vscode-cpptools

[Bug] cpptools fails to start on Ubuntu ARM64 due to missing execute permissions on shared libraries

Offen
#14,779 0 Kommentare 0 Reaktionen 1 zugewiesene Person Auf GitHub ansehen

@Colengms arbeitet bereits daran.

Seit 17.9.2026.

bug fixed Language Service regression
Vorherrschende Sprache
TypeScript
Sterne
6.2k
Forks
1.7k
Ø Merge
14 Std. 46 Min.
Gemergte PRs (30 T.)
61

Beschreibung

Type: Bug

Environment
OS: Ubuntu ARM64 (aarch64)
VS Code: Insiders / Remote-SSH
C/C++ Extension: 1.35.1-linux-arm64

Description
The cpptools server fails to start on remote ARM64 hosts because libc.so and libiconv.so lack execute permissions upon installation.

Workaround
Run the following on the remote host:

Bash
cd ~/.vscode-server-insiders/extensions/ms-vscode.cpptools-1.35.1-linux-arm64/bin
chmod +x libc.so libiconv.so

Extension version: 1.35.1
VS Code version: Code - Insiders 1.139.0-insider (046944034292b5479b4e9a50ad1a508033ffb64f, 2026-09-17T03:41:14Z)
OS version: Darwin arm64 23.6.0
Modes:
Remote OS version: Linux arm64 7.0.0-31-generic
Remote OS version: Linux arm64 7.0.0-31-generic

System Info
Item Value
CPUs Apple M3 (8 x 2400)
GPU Status 2d_canvas: enabled
GPU0: VENDOR= 0x106b [Google Inc. (Apple)], DEVICE=0x0000 [ANGLE (Apple, ANGLE Metal Renderer: Apple M3, Version 14.8.7 (Build 23J520))], DRIVER_VENDOR=Apple, DRIVER_VERSION=14.8.7 ACTIVE
Machine model name: Mac
Machine model version: 15.3
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: enabled_on
trees_in_viz: disabled_off
video_decode: enabled
video_encode: enabled
webgl: enabled
webgpu: enabled
webnn: disabled_off
Load (avg) 3, 2, 2
Memory (System) 16.00GB (0.28GB free)
Process Argv --crash-reporter-id 27be4519-1baa-4e03-9557-a29b120b07bc
Screen Reader no
VM 0%
Item Value
Remote SSH: 129
OS Linux arm64 7.0.0-31-generic
CPUs unknown (4 x 0)
Memory (System) 5.26GB (0.65GB free)
VM 100%
Item Value
Remote SSH: 129
OS Linux arm64 7.0.0-31-generic
CPUs unknown (4 x 0)
Memory (System) 5.26GB (0.65GB free)
VM 100%
A/B Experiments
vsliv368:30146709
pythonvspyt551:31249597
nativeloc1:31118317
dwcopilot:31158714
dwoutputs:31242946
copilot_t_ci:31333650
g012b348:31231168
pythonrdcb7:31268811
pythonpcpt1:31399616
6518g693:31302842
envsactivate1:31349248
editstats-enabled:31346256
cloudbuttont:31366566
3efgi100_wstrepl:31403338
ddidt:31398484
cp_cls_t_966_ss:31526232
4je02754:31565972
8hhj4413:31478653
cp_cls_c_1081:31454833
conptydll_true:31485575
e9c30283:31453065
c9b86496:31447327
ei9d7968:31462942
89g7j272:31506658
7e884298:31462391
i2gc6536:31472020
52612955:31508042
ddid_t:31478204
hmra_i5g22:31518061
7df3h592:31491241
cp_cls_t_1082:31535311
logging_enabled_new:31490725
jb_cp_cls_t_632:31543129
32d76977:31503652
ha629193:31508444
a1ije391_t:31533808
jbcp_cls_pctr_t:31531130
cp_intellij_t_nes:31548657
d7b18187:31526828
hide-eh-duplicates:31543293
replace-eh-with-ah:31545853
ihg5j128:31534457
sandbox-ui-on-2:31543161
nes-ex-cf-euporie-03:31542847
enable_editor_pane_layout:31551200
52258b4d:31547953
36h42362:31560305
c7c27ce7:31551212
1h923230:31564177
treatment-23-1:31555779
unuse_dynamic_mcp:31555281
0c1h4866:31562347
5b8j3302:31564600
autotiers:31584973
mangle-name-treatment:31568054
allow-signed-out:31574470
codex-agent-enabled:31566739
intellij_nes_preview_t:31580086
64a8d082:31573709
issue8950-5d26a188:31574957
39a5d156:31574988
ae8b2313:-9
2bfb8b39:31585911
soft:31581111
1cff76af:31580265
96d59efc:31580278
d601j348-suggestts7:31585349
links-treatment:31581067
7g328426_fixed:31583679
54hd3363:31585488
permission_prompt_treatment:1332566
ccr_pr_nudge_control:1319470
vsc_wsm_c:1324224
h5e14506_copy:1348995
ce50c479:1394169
3aced641:1389836
sem_714gi995:1394171

Beitragsleitfaden

Beitragsleitfaden öffnen

Erste Schritte

  1. Lies das ganze Issue und danach den Beitragsleitfaden des Projekts.
  2. Schreib ins Issue, dass du es übernimmst — das erspart doppelte Arbeit.
  3. Forke das Repository und arbeite in einem Branch.
  4. Öffne einen Pull Request, der die Issue-Nummer nennt.

Bewertung

Dieses Issue wurde noch nicht bewertet.

Neue Issues direkt in Ihr Postfach

Eine kurze Übersicht über anfängerfreundliche GitHub-Issues.