From: Tom Tromey <tom@tromey.com>
To: gdb-patches@sourceware.org
Subject: [FYI v2 0/2] Fix two Rust bugs [also for 8.2.1]
Date: Thu, 13 Sep 2018 17:01:00 -0000 [thread overview]
Message-ID: <20180913170109.30237-1-tom@tromey.com> (raw)
This is v2 of a patch I sent yesterday to fix a gdb crash with a
certain Rust program (and compiler).
This version addresses some of the comments Simon made. I've filed a
bug for further fixes, after the necessary version of rustc is
released.
I noticed one further buglet in this area, which is fixed by the
second patch.
Tested on x86-64 Fedora 28. I'm checking this in to the 8.2 branch as
well.
Tom
next reply other threads:[~2018-09-13 17:01 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-09-13 17:01 Tom Tromey [this message]
2018-09-13 17:01 ` [FYI v2 2/2] Make Rust error message mention the field name Tom Tromey
2018-09-13 17:01 ` [FYI v2 1/2] Fix crash with empty Rust enum 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=20180913170109.30237-1-tom@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;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).