From: Tom Tromey <tom@tromey.com>
To: Tom Tromey <tom@tromey.com>
Cc: gdb-patches@sourceware.org
Subject: Re: [RFA] Handle dereferencing Rust trait objects
Date: Wed, 15 Nov 2017 21:28:00 -0000 [thread overview]
Message-ID: <87o9o38c5k.fsf@tromey.com> (raw)
In-Reply-To: <20171115212403.8639-1-tom@tromey.com> (Tom Tromey's message of "Wed, 15 Nov 2017 14:24:03 -0700")
>>>>> "Tom" == Tom Tromey <tom@tromey.com> writes:
Tom> Objects that are referenced via a trait can't currently be inspected by
Tom> gdb. This patch implements the Rust equivalent of "set print object".
I forgot a couple of details.
The Rust compiler patch is here:
https://github.com/rust-lang/rust/pull/45897
It should go in soon.
I wasn't sure if I ought to xfail the new tests. I have the impression
that I'm the only person who runs the Rust gdb tests, but I'm not
actually certain.
Tom
next prev parent reply other threads:[~2017-11-15 21:28 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-11-15 21:24 Tom Tromey
2017-11-15 21:28 ` Tom Tromey [this message]
2017-11-16 16:40 ` Pedro Alves
2017-11-16 23:13 ` Tom Tromey
2017-11-17 15:39 ` Pedro Alves
2017-11-16 16:35 ` Pedro Alves
2017-11-16 23:26 ` Tom Tromey
2017-11-17 17:30 ` Tom Tromey
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=87o9o38c5k.fsf@tromey.com \
--to=tom@tromey.com \
--cc=gdb-patches@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