public inbox for gdb@sourceware.org
 help / color / mirror / Atom feed
From: Tom Tromey <tom@tromey.com>
To: Tom Tromey <tom@tromey.com>
Cc: Russell Mull <russell@digitalartificer.com>,  gdb@sourceware.org
Subject: Re: Regression or undocumented behavior change in Rust value printing in gdb 10.1
Date: Mon, 17 May 2021 12:21:56 -0600	[thread overview]
Message-ID: <878s4d2pbv.fsf@tromey.com> (raw)
In-Reply-To: <878s4h4e3w.fsf@tromey.com> (Tom Tromey's message of "Fri, 14 May 2021 07:52:19 -0600")

Russell> I'm tracking this on the Rust side at
Russell> https://github.com/rust-lang/rust/issues/85267, and have a small repro
Russell> available at https://github.com/mullr/gdb-pretty-test.

Tom> Thanks.  I'll take a look.

I pushed a fix for this the other day.

Tom

      reply	other threads:[~2021-05-17 18:21 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-05-14  0:07 Russell Mull
2021-05-14 13:52 ` Tom Tromey
2021-05-17 18:21   ` Tom Tromey [this message]

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=878s4d2pbv.fsf@tromey.com \
    --to=tom@tromey.com \
    --cc=gdb@sourceware.org \
    --cc=russell@digitalartificer.com \
    /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).