From: Tom Tromey <tromey@redhat.com>
To: Andrew Pinski <pinskia@gmail.com>
Cc: Andreas Schwab <schwab@linux-m68k.org>,
"gdb-patches\@sourceware.org" <gdb-patches@sourceware.org>
Subject: Re: [PATCH/AARCH64] Fix hardware break points
Date: Mon, 29 Jul 2013 17:56:00 -0000 [thread overview]
Message-ID: <877gg9p7w1.fsf@fleche.redhat.com> (raw)
In-Reply-To: <CA+=Sn1k=30-Y=MFEq3gVcDR9xugWsMWpHi8_a79hCUX6vxjEEw@mail.gmail.com> (Andrew Pinski's message of "Sat, 27 Jul 2013 15:42:49 -0700")
>>>>> "Andrew" == Andrew Pinski <pinskia@gmail.com> writes:
Andrew> Here is the fixed one which was definitely tested.
It seems reasonable to me, but I think that gdbserver needs a parallel
fix.
Just add it to the list of concrete reasons to merge the back ends...
Tom
next prev parent reply other threads:[~2013-07-29 17:56 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-07-27 20:13 Andrew Pinski
2013-07-27 21:34 ` Andreas Schwab
2013-07-27 22:42 ` Andrew Pinski
2013-07-29 17:56 ` Tom Tromey [this message]
2013-09-10 14:38 ` Will Newton
2013-09-12 7:15 ` Andrew Pinski
2013-09-16 12:44 ` Pedro Alves
2013-09-16 12:53 ` Will Newton
2013-09-16 13:38 ` Pedro Alves
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=877gg9p7w1.fsf@fleche.redhat.com \
--to=tromey@redhat.com \
--cc=gdb-patches@sourceware.org \
--cc=pinskia@gmail.com \
--cc=schwab@linux-m68k.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