Mirror of the gdb-patches mailing list
 help / color / mirror / Atom feed
From: Joel Brobecker <brobecker@adacore.com>
To: Emi SUZUKI <emi-suzuki@tjsys.co.jp>
Cc: gdb-patches@sourceware.org
Subject: Re: Watchpoint on an unloaded shared library(1)
Date: Mon, 22 Dec 2008 03:28:00 -0000	[thread overview]
Message-ID: <20081222032758.GA2835@adacore.com> (raw)
In-Reply-To: <20081221131036.GB25416@adacore.com>

> > > How about replace all the code that's inside
> > > 
> > >   if (bpt->type == bp_watchpoint || 
> > >       bpt->type == bp_hardware_watchpoint ||
> > >       bpt->type == bp_read_watchpoint ||
> > >       bpt->type == bp_access_watchpoint)
> > >     {
> > >       [re-create a lot of stuff for our watchpoint...]
> > > 
> > > by a call to update_watchpoint (bpt, 1)?  Would that work in your case? 
> > 
> > It works without merging the missing code each other, as long as we
> > don't have to care the hardware watchpoint resource count here: if the
> > user sets other watchpoints while the disabled hardware watchpoints
> > exist, re-enabling the disabled ones might fail out of the shortage of
> > resources.  
> 
> That's a good point.

As it turns out, I think we just got lucky thanks to Jan:
http://www.sourceware.org/ml/gdb-patches/2008-12/msg00363.html.

update_watchpoint now automagically downgrades hardware watchpoints
into a software watchpoints if needed. So we can get rid of that part.
So all we have to do, now is:

>    if (bpt->type == bp_watchpoint || 
>        bpt->type == bp_hardware_watchpoint ||
>        bpt->type == bp_read_watchpoint ||
>        bpt->type == bp_access_watchpoint)
>      {
>        struct gdb_exception e;
> 
>        TRY_CATCH (e, RETURN_MASK_ALL)
>          {
>            update_watchpoint (...);
>          }
>        if (e.reason < 0)
>          {
>            exception_fprintf (gdb_strerr, e, "Cannot enable watchpoint %d:",
>                               b->number);
>            return;
>          }

-- 
Joel


  reply	other threads:[~2008-12-22  3:28 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-11-20 18:25 Emi SUZUKI
2008-12-13 15:06 ` Joel Brobecker
2008-12-16 12:16   ` Emi SUZUKI
2008-12-21 13:11     ` Joel Brobecker
2008-12-22  3:28       ` Joel Brobecker [this message]
2008-12-25 11:28         ` Emi SUZUKI
2008-12-26  6:11           ` Joel Brobecker
2008-12-26  7:09             ` Emi SUZUKI
2008-12-28 11:48               ` Joel Brobecker
2009-01-06  1:47                 ` Emi SUZUKI
2009-01-06  4:28                   ` Joel Brobecker
2009-01-06  5:16                     ` Emi SUZUKI
2009-01-08  4:02                     ` [commit] " Emi SUZUKI

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=20081222032758.GA2835@adacore.com \
    --to=brobecker@adacore.com \
    --cc=emi-suzuki@tjsys.co.jp \
    --cc=gdb-patches@sourceware.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