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

Hello Joel, 

From: Joel Brobecker <brobecker at adacore.com>
Subject: Re: Watchpoint on an unloaded shared library(1)
Date: Mon, 22 Dec 2008 07:27:58 +0400

>> > > 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;
>>          }

This does work for me, except one duplication of the codes (that you
may have noticed already):

  static void
  do_enable_breakpoint (struct breakpoint *bpt, enum bpdisp disposition)
  {
    int target_resources_ok, other_type_used;
    struct value *mark;
  
    if (bpt->type == bp_hardware_breakpoint)
      {
        int i;
        i = hw_breakpoint_used_count ();
        target_resources_ok = 
          TARGET_CAN_USE_HARDWARE_WATCHPOINT (bp_hardware_breakpoint, 
                                              i + 1, 0);
        if (target_resources_ok == 0)
          error (_("No hardware breakpoint support in the target."));
        else if (target_resources_ok < 0)
          error (_("Hardware breakpoints used exceeds limit."));
      }

That should be done in update_watchpoint.  

I would try to address incapabilities on PPC after those codes are
committed.  Thank you for taking care of it!


I wonder if I should greet for Christmas here...
-- 
Emi SUZUKI / emi-suzuki at tjsys.co.jp


  reply	other threads:[~2008-12-25 11: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
2008-12-25 11:28         ` Emi SUZUKI [this message]
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=20081225.202730.01371998.emi-suzuki@tjsys.co.jp \
    --to=emi-suzuki@tjsys.co.jp \
    --cc=brobecker@adacore.com \
    --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