microsoft / microsoft/vscode-cpptools
Why should binary data be displayed in octal instead of hexadecimal?
Nobody has claimed this yet.
- Dominant language
- TypeScript
- Stars
- 6.2k
- Forks
- 1.7k
- Avg merge
- 14h 46m
- Merged PRs (30d)
- 61
Description
Issue Type: Bug
md5
[0]:17 '\021'
[1]:33 '!'
[2]:136 '\210'
[3]:166 '\246'
[4]:178 '\262'
[5]:198 '\306'
[6]:168 '\250'
[7]:102 'f'
[8]:46 '.'
[9]:168 '\250'
[10]:126 '~'
[11]:11 '\v'
[12]:242 '\362'
[13]:168 '\250'
[14]:188 '\274'
[15]:144 '\220'
Extension version: 0.28.1
VS Code version: Code 1.45.1 (5763d909d5f12fe19f215cbfdd29a91c0fa9208a, 2020-05-14T08:27:22.494Z)
OS version: Linux x64 5.3.0-3-amd64
System Info
| Item | Value |
|---|---|
| CPUs | AMD Ryzen 7 3750H with Radeon Vega Mobile Gfx (8 x 1775) |
| GPU Status | 2d_canvas: enabled flash_3d: enabled flash_stage3d: enabled flash_stage3d_baseline: enabled gpu_compositing: enabled multiple_raster_threads: enabled_on oop_rasterization: disabled_off protected_video_decode: unavailable_off rasterization: disabled_software skia_renderer: disabled_off_ok video_decode: unavailable_off viz_display_compositor: enabled_on viz_hit_test_surface_layer: disabled_off_ok webgl: enabled webgl2: enabled |
| Load (avg) | 1, 1, 2 |
| Memory (System) | 14.66GB (0.49GB free) |
| Process Argv | --no-sandbox --unity-launch |
| Screen Reader | no |
| VM | 0% |
| DESKTOP_SESSION | deepin |
| XDG_CURRENT_DESKTOP | Deepin |
| XDG_SESSION_DESKTOP | deepin |
| XDG_SESSION_TYPE | x11 |
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start by reproducing the reported binary-data display with the provided md5 sample in VS Code 1.45.1 and the C/C++ extension. Trace the extension's debugger or binary-value display path to determine why octal is selected; done means the display behavior and expected hexadecimal representation are clearly established and covered by an appropriate check.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- cpp, typescript
- Domain
- devtools
- Issue type
- Bug
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100