[Bug remote/30618] warning: while parsing threads: not well-formed (invalid token) - in non-stop + remote mode

["cvs-commit at gcc dot gnu.org" <sourceware-bugzilla@sourceware.org>]

https://sourceware.org/bugzilla/show_bug.cgi?id=30618

--- Comment #6 from cvs-commit at gcc dot gnu.org <cvs-commit at gcc dot gnu.org> ---
The master branch has been updated by Tom Tromey <tromey@sourceware.org>:

https://sourceware.org/git/gitweb.cgi?p=binutils-gdb.git;h=07b3255c3bae7126a0d679f957788560351eb236

commit 07b3255c3bae7126a0d679f957788560351eb236
Author: Tom Tromey <tom@tromey.com>
Date:   Thu Jul 13 17:28:48 2023 -0600

    Filter invalid encodings from Linux thread names

    On Linux, a thread can only be 16 bytes (including the trailing \0).
    A user sent in a test case where this causes a truncated UTF-8
    sequence, causing gdbserver to create invalid XML.

    I went back and forth about different ways to solve this, and in the
    end decided to fix it in gdbserver, with the reason being that it
    seems important to generate correct XML for the <thread> response.

    I am not totally sure whether the call to setlocale could have
    unplanned consequences.  This is needed, though, for nl_langinfo to
    return the correct result.

    Bug: https://sourceware.org/bugzilla/show_bug.cgi?id=30618

-- 
You are receiving this mail because:
You are on the CC list for the bug.