From: Edjunior Barbosa Machado <emachado@linux.vnet.ibm.com>
To: Pedro Alves <pedro@codesourcery.com>
Cc: gdb-patches@sourceware.org
Subject: Re: [5/6] breakpoints_ops for all kinds of breakpoints: new watchpoints instance type
Date: Wed, 27 Jul 2011 10:11:00 -0000 [thread overview]
Message-ID: <4E2FBC5E.3020409@linux.vnet.ibm.com> (raw)
In-Reply-To: <201107221645.06432.pedro@codesourcery.com>
On 07/22/2011 12:45 PM, Pedro Alves wrote:
> Move the watchpoints-only fields in struct breakpoint
> to a new struct watchpoint, as a subclass of struct breakpoint,
> to go with the move of watchpoints to breakpoint_ops done a
> while ago.
>
Hi,
it seems a couple of testcases started failing on ppc64 after apply this patch:
FAIL: gdb.base/recurse.exp: continue to second instance watchpoint, first time
(and subsequent tests on recurse.exp, due to this first failure)
FAIL: gdb.base/watchpoint.exp: next over buffer set
...
FAIL: gdb.base/watchpoint.exp: next over global_ptr_ptr buffer set
FAIL: gdb.base/watchpoint.exp: next over global_ptr_ptr pointer advance
One quickly noticed difference is that, according to gdb output, these failing watchpoints became hardware watchpoints after this patch. I'm still trying to figure out why this is happening.
Regards,
--
Edjunior
next prev parent reply other threads:[~2011-07-27 7:21 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-07-22 15:58 Pedro Alves
2011-07-27 10:11 ` Edjunior Barbosa Machado [this message]
2011-09-12 15:06 ` Watchpoint resource accounting broken (Re: [5/6] breakpoints_ops for all kinds of breakpoints: new watchpoints instance type) Ulrich Weigand
2011-09-12 15:17 ` Pedro Alves
2011-09-12 15:23 ` Edjunior Barbosa Machado
2011-09-13 14:16 ` Pedro Alves
2011-09-13 14:42 ` Edjunior Barbosa Machado
2011-09-13 14:54 ` Pedro Alves
2011-09-13 16:49 ` Watchpoint resource accounting broken (Re: [5/6] breakpoints_ops for all kinds of breakpoints: new watchpoints instance type Ulrich Weigand
2011-09-13 17:20 ` 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=4E2FBC5E.3020409@linux.vnet.ibm.com \
--to=emachado@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