You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Replace utf8 package with using TextDecoder API (#466)
This fixes the assumption that every GDB on every host supports
and starts up with UTF-8 host charset. This caused errors if this is
not the case.
* Replace use of utf8 package with TextDecoder API.
* Detect and use host charset encoding and apply
it to octal char sequences. Updates with each charset change.
* Synchronize changed charsets between MAIN and AUX GDB
backends.
* Add fixup map for encodings not known to whatwg standard,
e.g. Windows CP65001 which effectively is utf-8.
* Explicitly set charset to UTF-8 for Windows unicode path test,
we may have a machine/GDB combination which uses CP1252 if 'auto'.
---------
Signed-off-by: Jens Reinecke <jens.reinecke@arm.com>
Copy file name to clipboardExpand all lines: CHANGELOG.md
+4Lines changed: 4 additions & 0 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -1,5 +1,9 @@
1
1
# Change Log
2
2
3
+
## Unreleased
4
+
5
+
- Fixes [`465`](https://github.com/eclipse-cdt-cloud/cdt-gdb-adapter/issues/465): UTF-8 'Failed to decode cstring' errors for GDB with CP1252 support only.
6
+
3
7
## 1.4.1
4
8
5
9
- Fixes [`400`](https://github.com/eclipse-cdt-cloud/cdt-gdb-adapter/issues/400): Evaluation of variables to support RTOS Views extension.
0 commit comments