Mirror of the gdb-patches mailing list
 help / color / mirror / Atom feed
From: Thiago Jung Bauermann <bauerman@br.ibm.com>
To: Pedro Alves <pedro@codesourcery.com>
Cc: gdb-patches@sourceware.org,
	       Philippe Waroquiers <philippe.waroquiers@skynet.be>,
	       yao@codesourcery.com
Subject: Re: software watchpoints bug (was: Re: x86 watchpoints bug)
Date: Wed, 27 Jul 2011 03:45:00 -0000	[thread overview]
Message-ID: <1311730148.12326.2.camel@hactar> (raw)
In-Reply-To: <201107262046.19451.pedro@codesourcery.com>

On Tue, 2011-07-26 at 20:46 +0100, Pedro Alves wrote:
> On Saturday 23 July 2011 03:38:55, Thiago Jung Bauermann wrote:
> > On Fri, 2011-07-22 at 17:40 +0100, Pedro Alves wrote:
> 
> > > Maybe better would be to change works_in_software_mode_watchpoint to:
> > > 
> > > int
> > > works_in_software_mode_watchpoint (const struct breakpoint *b)
> > > {
> > > -  return b->type == bp_hardware_watchpoint;
> > > +  return (b->type == bp_watchpoint || b->type == bp_hardware_watchpoint);
> > > }
> > 
> > Agreed. I would only comment that the parenthesis are not necessary. :-)
> 
> Alright! :-)  I've applied the patch below, which does that, and
> adds a new test.

Great, thanks for the patch.
 
> > Theoretically resources_needed_watchpoint would have to be adapted for
> > software watchpoints too, but in practice that function is only called
> > in hw_watchpoint_used_count, which is never called with bp_watchpoint as
> > an argument.
> > 
> > FWIW, my local branch with my rework of debug registers accounting
> > doesn't have hw_watchpoint_used_count anymore.
> 
> Oooh!  Is that branch somewhere public?

Not yet. I think I just finished ironing out the bugs from my changes
related to watchpoints. I'm now starting to work on breakpoints.

I was thinking of posting the watchpoints patch as an RFC. I'll rebase
the branch on top of current master to get your breakpoint_ops changes
(great work BTW) and post it.
-- 
[]'s
Thiago Jung Bauermann
IBM Linux Technology Center


  reply	other threads:[~2011-07-27  1:29 UTC|newest]

Thread overview: 32+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-05-21 22:20 ping: Re: PATCH : allow to set length of hw watchpoints (e.g. for Valgrind gdbserver) Philippe Waroquiers
2011-05-26 19:02 ` Tom Tromey
2011-05-29 13:01   ` Philippe Waroquiers
2011-05-30 15:26     ` Joel Brobecker
2011-05-31 19:07     ` x86 watchpoints bug (Re: ping: Re: PATCH : allow to set length of hw watchpoints (e.g. for Valgrind gdbserver)) Pedro Alves
2011-05-31 20:25       ` Philippe Waroquiers
2011-05-31 20:53         ` Pedro Alves
2011-05-31 21:29       ` Pedro Alves
2011-05-31 22:15         ` Philippe Waroquiers
2011-05-31 23:04           ` Pedro Alves
2011-06-01 14:35             ` Pedro Alves
2011-06-08 22:55               ` Philippe Waroquiers
2011-06-09  0:00                 ` Pedro Alves
2011-06-09 22:16                   ` Philippe Waroquiers
2011-07-21 17:20                     ` Pedro Alves
2011-07-22 16:40                       ` Philippe Waroquiers
2011-07-22 16:43                         ` Pedro Alves
2011-07-23 16:28                           ` Thiago Jung Bauermann
2011-07-26 20:02                             ` software watchpoints bug (was: Re: x86 watchpoints bug) Pedro Alves
2011-07-27  3:45                               ` Thiago Jung Bauermann [this message]
2011-07-22 17:19                         ` x86 watchpoints bug (Re: ping: Re: PATCH : allow to set length of hw watchpoints (e.g. for Valgrind gdbserver)) Pedro Alves
2011-05-27  3:25 ` ping: Re: PATCH : allow to set length of hw watchpoints (e.g. for Valgrind gdbserver) Yao Qi
2011-05-27 17:53   ` Tom Tromey
2011-05-27 17:59     ` Pedro Alves
2011-05-30  4:06       ` Yao Qi
2011-05-30  5:34         ` Philippe Waroquiers
2011-05-30  5:48           ` Yao Qi
2011-05-30  6:31             ` Philippe Waroquiers
2011-05-31 17:31         ` Pedro Alves
2011-05-31 18:06           ` Philippe Waroquiers
2011-06-01 15:15             ` Pedro Alves
2011-06-05 20:55               ` Philippe Waroquiers

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=1311730148.12326.2.camel@hactar \
    --to=bauerman@br.ibm.com \
    --cc=gdb-patches@sourceware.org \
    --cc=pedro@codesourcery.com \
    --cc=philippe.waroquiers@skynet.be \
    --cc=yao@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