The conversations in eclipse-cdt-cloud/cdt-gdb-adapter#523 (comment) today made me realize there is a small (potential) bug with how output radix is set. Perhaps this has been covered/discussed enough, but I wanted to raise it in a new issue instead of losing the information
In:
|
expression: `> set output-radix ${radix === 'hexadecimal' ? 16 : 10}`, |
The GDB docs recommend always setting radix unambiguously (or using input, but we don't know what that is). The use of 10 and 16 are both ambigious. link
For example, changing the code to:
expression: `> set output-radix ${radix === 'hexadecimal' ? 16. : 10.}`, or
expression: `> set output-radix ${radix === 'hexadecimal' ? 0x10 : 0xa}`, would do it.
The conversations in eclipse-cdt-cloud/cdt-gdb-adapter#523 (comment) today made me realize there is a small (potential) bug with how output radix is set. Perhaps this has been covered/discussed enough, but I wanted to raise it in a new issue instead of losing the information
In:
cdt-gdb-vscode/src/switchRadix.ts
Line 39 in ae6bb90
The GDB docs recommend always setting radix unambiguously (or using input, but we don't know what that is). The use of
10and16are both ambigious. linkFor example, changing the code to:
or
would do it.