microsoft / microsoft/vscode-cpptools

Binary Data viewer not working

Open
#12,950 2 comments 2 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

debugger help wanted Visual Studio Code
Dominant language
TypeScript
Stars
6.2k
Forks
1.7k
Avg merge
14h 46m
Merged PRs (30d)
61

Description

Type: Bug

When trying to view binary data for s pointer in this simple program:

#include <stdio.h>
#include <stdlib.h>
#include <string.h>

void print_string(char *s) {
	for (int i = 0; s[i] != '\0'; i++) {
		putc(s[i], stdout);
	}
	putc('\n', stdout);
}

int main(int argc, char **argv) {
	int n[3] = {0x616C6F48, 0x6E754D20, 0x6F64};
	print_string(n);
	return 0;
}

I'm getting this error:

The editor could not be opened due to an unexpected error: Unable to read file 'vscode-debug-memory://66fed0a8-55f7-44a3-8067-652795f4b3c4/0x00007fffffffd54c/memory.bin' (CodeExpectedError: Arithmetic operation resulted in an overflow.)

Extension version: 1.23.1
VS Code version: Code 1.95.1 (65edc4939843c90c34d61f4ce11704f09d3e5cb6, 2024-10-31T05:14:54.222Z)
OS version: Windows_NT x64 10.0.22631
Modes:
Remote OS version: Linux x64 5.15.90.1-microsoft-standard-WSL2

System Info
Item Value
CPUs 11th Gen Intel(R) Core(TM) i7-1165G7 @ 2.80GHz (8 x 2803)
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
vulkan: disabled_off
webgl: enabled
webgl2: enabled
webgpu: enabled
webnn: disabled_off
Load (avg) undefined
Memory (System) 39.80GB (15.13GB free)
Process Argv --folder-uri=vscode-remote://wsl+Ubuntu-22.04/home/aranieri/sisop/prueba-c --remote=wsl+Ubuntu-22.04 --crash-reporter-id ffc230d8-3622-441f-a972-8e0f91fa8acf
Screen Reader no
VM 0%
Item Value
Remote WSL: Ubuntu-22.04
OS Linux x64 5.15.90.1-microsoft-standard-WSL2
CPUs 11th Gen Intel(R) Core(TM) i7-1165G7 @ 2.80GHz (8 x 0)
Memory (System) 7.76GB (5.42GB free)
VM 0%
A/B Experiments
vsliv368cf:30146710
vspor879:30202332
vspor708:30202333
vspor363:30204092
vswsl492:30256859
vscod805cf:30301675
binariesv615:30325510
vsaa593cf:30376535
py29gd2263:31024239
c4g48928:30535728
azure-dev_surveyone:30548225
2i9eh265:30646982
962ge761:30959799
pythongtdpath:30769146
pythonnoceb:30805159
asynctok:30898717
pythonmypyd1:30879173
2e7ec940:31000449
pythontbext0:30879054
cppperfnew:31000557
dsvsc020:30976470
pythonait:31006305
dsvsc021:30996838
bdiig495:31013172
dvdeprecation:31068756
dwnewjupyter:31046869
newcmakeconfigv2:31071590
impr_priority:31102340
nativerepl2:31139839
refactort:31108082
pythonrstrctxt:31112756
nativeloc2:31134642
cf971741:31144450
iacca1:31171482
notype1:31157159
5fd0e150:31155592
dwcopilot:31170013

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.

Research direction

Reproduce the failure in the VS Code C/C++ extension using the supplied C++ program and the vscode-debug-memory:// binary viewer URI. Trace the binary data viewer from the memory-open request to the arithmetic overflow, then verify that the viewer opens the requested memory without the reported error.

Written by the indexing model from the issue text.

Assessment

Tech stack
cpp, typescript, vscode
Domain
devtools
Issue type
Bug
Difficulty
4/5
Estimated time
3-5 days
Activity status
Stale
Clarity
Mostly clear
Newbie friendliness
32/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.