From: Joel Brobecker <brobecker@adacore.com>
To: Will Newton <will.newton@linaro.org>
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 13:40:00 -0000 [thread overview]
Message-ID: <20131125130250.GE3114@adacore.com> (raw)
In-Reply-To: <CANu=DmiprxHcpNHVNqZt4BYUH_YoswKYgh0Q=EQe4xf=x4TLRA@mail.gmail.com>
> > We're about to create a 7.6.2 release. To help me sent release
> > announcements, I need an entry in the wiki page we created for
> > that release branch. For 7.6.2, that's:
> >
> > https://sourceware.org/gdb/wiki/GDB_7.6_Release
> >
> > Can you please add an entry that follows the format used in
> > the entries added for the 7.6.1 release?
>
> Sure, no problem.
Thanks!
> > I tried doing that myself, but got lost a little. AFAICT, you're
> > applying the same patch as one that was applied on the GDB side.
> > I traced the problem description back to a patch first posted in
> > July, but: 1. Does your patch fix the same problem/symptoms?
>
> It fixes the same issue in gdbserver that was fixed in gdb.
>
> > 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.
Thanks again!
--
Joel
next prev parent reply other threads:[~2013-11-25 13:03 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 [this message]
2013-11-25 15:24 ` Will Newton
2013-11-25 15:46 ` Joel Brobecker
2013-11-25 15:55 ` Will Newton
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=20131125130250.GE3114@adacore.com \
--to=brobecker@adacore.com \
--cc=gdb-patches@sourceware.org \
--cc=will.newton@linaro.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