From: Will Newton <will.newton@linaro.org>
To: Joel Brobecker <brobecker@adacore.com>
Cc: "gdb-patches@sourceware.org" <gdb-patches@sourceware.org>
Subject: Re: gdbserver, aarch64: Zero out regs in aarch64_linux_set_debug_regs
Date: Mon, 25 Nov 2013 15:55:00 -0000 [thread overview]
Message-ID: <CANu=DmgTg+uVhV7qNRTbXuRBvCJ0jW-xq_4qCvF4_q64oYyEbw@mail.gmail.com> (raw)
In-Reply-To: <20131125152414.GG3114@adacore.com>
On 25 November 2013 15:24, Joel Brobecker <brobecker@adacore.com> wrote:
>> >> > 2. The gdb-side patch in not part of the gdb_7_6-branch;
>> >> > is that what we want?
>> >>
>> >> Not really! I believed that the gdb patch had been committed to the
>> >> stable branch but later discovered that it hadn't. As the stable
>> >> branch appeared to be dormant I didn't follow up on it. Ideally both
>> >> patches should be applied and if we are going to do another release
>> >> I'm happy to cherry pick it across.
>> >
>> > Let's do that, then. I think it'll make better sense for the user,
>> > and it'll also be easier to describe the extent of the problem being
>> > fixed.
>>
>> Just to confirm - this patch should be applied to the gdb_7_6-branch in CVS?
>
> In the git repository, actually (CVS is closed, and I will be making
> the new release using the git repo).
Ok, cherry-picked and pushed. I also updated the wiki. Unfortunately
there doesn't seem to be a PR for the issue.
--
Will Newton
Toolchain Working Group, Linaro
next prev parent reply other threads:[~2013-11-25 15:46 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-11-25 13:03 Joel Brobecker
2013-11-25 13:07 ` Will Newton
2013-11-25 13:40 ` Joel Brobecker
2013-11-25 15:24 ` Will Newton
2013-11-25 15:46 ` Joel Brobecker
2013-11-25 15:55 ` Will Newton [this message]
2013-11-26 4:56 ` Joel Brobecker
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='CANu=DmgTg+uVhV7qNRTbXuRBvCJ0jW-xq_4qCvF4_q64oYyEbw@mail.gmail.com' \
--to=will.newton@linaro.org \
--cc=brobecker@adacore.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