From: Luis Machado <luisgpm@linux.vnet.ibm.com>
To: Pedro Alves <pedro@codesourcery.com>
Cc: gdb-patches@sourceware.org
Subject: Re: [PATCH] testcases: Fix assorted problems related to powerpc
Date: Wed, 29 Sep 2010 15:04:00 -0000 [thread overview]
Message-ID: <1285730309.3709.0.camel@gargoyle> (raw)
In-Reply-To: <201009281708.26790.pedro@codesourcery.com>
Thanks Pedro.
That patch does fix the problem. I'll send an updated patch without
fixes to watch-read.exp.
Luis
On Tue, 2010-09-28 at 17:08 +0100, Pedro Alves wrote:
> On Tuesday 28 September 2010 16:57:01, Luis Machado wrote:
> > gdb.base/watch-read.exp tries to create both a HW write watchpoint and a
> > HW read watchpoint, but since POWER server processors only support a
> > single HW watchpoint, this doesn't work right. It's strange, though,
> > that GDB actually creates two HW watches for ppc, but the last one
> > overrides the read/write flags of the previous one and thus we miss
> > triggers. I've used an awatch instead, though i'd have to check if GDB
> > is doing something wrong and if we could make this testcase pass without
> > any changes. The results with AWATCH are pretty much the same as with
> > RWATCH + WATCH.
> >
>
> GDB is doing something wrong, and it's possible to make ppc pass this
> testcase without any (test) changes. I think the patch below is what
> I used to test on ppc when I wrote that test
> (<http://sourceware.org/ml/gdb-patches/2010-02/msg00521.html>), and
> the test passed with it.
>
next prev parent reply other threads:[~2010-09-29 3:25 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-09-28 21:47 Luis Machado
2010-09-28 21:48 ` Pedro Alves
2010-09-29 15:04 ` Luis Machado [this message]
2010-09-29 16:32 Luis Machado
2010-11-09 4:47 ` Jan Kratochvil
2010-11-09 5:46 ` Doug Evans
2010-11-27 22:09 ` Andreas Schwab
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=1285730309.3709.0.camel@gargoyle \
--to=luisgpm@linux.vnet.ibm.com \
--cc=gdb-patches@sourceware.org \
--cc=pedro@codesourcery.com \
/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).