public inbox for gdb-prs@sourceware.org
help / color / mirror / Atom feed
From: "cvs-commit at gcc dot gnu.org" <sourceware-bugzilla@sourceware.org>
To: gdb-prs@sourceware.org
Subject: [Bug gdb/31153] [native-gdbserver] FAIL: gdb.ada/tasks.exp: info threads
Date: Tue, 09 Jan 2024 14:14:16 +0000	[thread overview]
Message-ID: <bug-31153-4717-JsnELNZY2m@http.sourceware.org/bugzilla/> (raw)
In-Reply-To: <bug-31153-4717@http.sourceware.org/bugzilla/>

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

--- Comment #3 from Sourceware Commits <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=862180a2d10963494356ec089a16b808bab736bd

commit 862180a2d10963494356ec089a16b808bab736bd
Author: Tom Tromey <tromey@adacore.com>
Date:   Fri Dec 15 07:56:45 2023 -0700

    Fix two bugs in gdbserver thread name handling

    Simon pointed out that my earlier patch to gdbserver's thread name
    code:

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

            Filter invalid encodings from Linux thread names

    ... introduced a regression.  This bug was that the iconv output was
    not \0-terminated.

    Looking at it, I found another bug as well -- replace_non_ascii would
    not \0-terminate, and also would return the wrong pointer

    This patch fixes both of them.

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

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

  parent reply	other threads:[~2024-01-09 14:14 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-12-12 21:04 [Bug gdb/31153] New: " simon.marchi at polymtl dot ca
2023-12-12 23:56 ` [Bug gdb/31153] " tromey at sourceware dot org
2023-12-15 15:02 ` tromey at sourceware dot org
2024-01-09 14:14 ` cvs-commit at gcc dot gnu.org [this message]
2024-01-09 14:15 ` tromey at sourceware dot org

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=bug-31153-4717-JsnELNZY2m@http.sourceware.org/bugzilla/ \
    --to=sourceware-bugzilla@sourceware.org \
    --cc=gdb-prs@sourceware.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body. 
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).