From: Pedro Alves <palves@redhat.com>
To: Kyle Huey <me@kylehuey.com>, gdb@sourceware.org
Cc: rr-dev <rr-dev@mozilla.org>
Subject: Re: [regression] gdb 7.11 breaks rr
Date: Tue, 17 May 2016 16:27:00 -0000 [thread overview]
Message-ID: <4ec4cc6e-3bfd-6974-3a82-64c36799eb30@redhat.com> (raw)
In-Reply-To: <CAP045Ao2usw07e0iUJ7jfYp8EHCBKBTw6UvGZFVDrD-0Xq54JA@mail.gmail.com>
On 05/16/2016 11:06 PM, Kyle Huey wrote:
> This was fixed after the release of gdb 7.11 by [1]. I verified that
> cherry-picking this commit on top of the gdb-7.11-release tag also fixes
> rr. Could we get this commit backported for a 7.11.1?
It actually was already, at the time:
https://sourceware.org/ml/gdb-patches/2016-04/msg00277.html
Git commit 6b9ef0d488c556339aea7b095ef7a9b6bf6b1af1.
Try the gdb-7.11-branch branch (where 7.11.1 will be released from),
instead of the 7.11 release tag, which is frozen.
Thanks,
Pedro Alves
next prev parent reply other threads:[~2016-05-17 16:27 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-05-16 22:06 Kyle Huey
2016-05-17 16:27 ` Pedro Alves [this message]
2016-05-17 18:02 ` Kyle Huey
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=4ec4cc6e-3bfd-6974-3a82-64c36799eb30@redhat.com \
--to=palves@redhat.com \
--cc=gdb@sourceware.org \
--cc=me@kylehuey.com \
--cc=rr-dev@mozilla.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