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: Sat, 13 Dec 2008 15:06:00 -0000	[thread overview]
Message-ID: <20081213150517.GE6866@adacore.com> (raw)
In-Reply-To: <20081120.210657.01365938.emi-suzuki@tjsys.co.jp>

Emi,

Thanks for sending this patch.

> 2008-11-20  Emi Suzuki	<emi-suzuki@tjsys.co.jp>
> 
> 	* breakpoint.c (do_enable_breakpoint): Inform the user and
> 	return from the function if the expression of a watchpoint is
> 	invalid and cannot be updated.  

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? 

When I looked at what update_watchpoint does and what do_enable_breakpoint
does for watchpoints, it seemed to me that do_enable_breakpoint was trying
to do the same, except that it was missing a few pieces. Does anybody see
a reason for the code almost-duplication here?

-- 
Joel


  reply	other threads:[~2008-12-13 15:06 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 [this message]
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
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=20081213150517.GE6866@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