| commit | bfdb52f83ca6ca3a0eb43ef2bd0f4f8193a06472 | [log] [tgz] |
|---|---|---|
| author | Tom Tromey <tromey@adacore.com> | Tue Apr 19 11:21:35 2022 -0600 |
| committer | Tom Tromey <tromey@adacore.com> | Tue Apr 26 12:54:05 2022 -0600 |
| tree | d272d3d9dca9e3864d38eaf4e7f0232a4e937b40 | |
| parent | f93c6e0a2ed1ad4f0a9bb8f38e859f3312c25282 [diff] |
Handle encoding failures in Windows thread names Internally at AdaCore, we noticed that the new Windows thread name code could fail. First, it might return a zero-length string, but in gdb conventions it should return nullptr instead. Second, an encoding failure could wind up showing replacement characters to the user; this is confusing and not useful; it's better to recognize such errors and simply discard the name. This patch makes both of these changes.