UTF-8 start byte cannot be 0xff.
Off-by-1 bug is possible. Maybe a hidden control character is throwing off the
count but being stripped away prior to the attempt to convert to UTF-8.
On Apr 17, 2024, at 1:13 PM, Joel Sherrill <j...@rtems.org> wrote:
Hi
6.1rc3 appears to be in pretty good shape on CentOS 7 (w/GCC 8 and Python 3
SCL). Results should be on the build@ list. One odd issue appears to be in the
rtems-tester.
Testing a riscv-bsp with spike, I get this output. It is repeated with other
spike/risc-v bsp tests. Any ideas?
Exception in thread _stdout[spike]:
Traceback (most recent call last):
File "/opt/rh/rh-python36/root/usr/lib64/python3.6/threading.py", line 916,
in _bootstrap_inner
self.run()
File "/opt/rh/rh-python36/root/usr/lib64/python3.6/threading.py", line 864,
in run
self._target(*self._args, **self._kwargs)
File "/home/joel/rtems-6.1rc3/tools/6/share/rtems/rtemstoolkit/execute.py",
line 226, in _readthread
data = data.decode(sys.stdout.encoding)
UnicodeDecodeError: 'utf-8' codec can't decode byte 0xff in position 0: invalid
start byte
_______________________________________________
devel mailing list
devel@rtems.org
http://lists.rtems.org/mailman/listinfo/devel
