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: Sun, 28 Dec 2008 11:48:00 -0000 [thread overview]
Message-ID: <20081228111719.GC4216@adacore.com> (raw)
In-Reply-To: <20081226.160820.01367812.emi-suzuki@tjsys.co.jp>
> > Not quite: As you can see, this part of the code deals with hardware
> > *breakpoints*, not watchpoints.
>
> Shame on me... I've totally missed that :-(
Believe me, I've done way worse and I am pretty sure it will happen
to me again (we're only human after all).
> 2008-12-26 Joel Brobecker <brobecker@adacore.com>
> Emi Suzuki <emi-suzuki@tjsys.co.jp>
>
> * breakpoint.c (do_enable_breakpoint): Use update_watchpoint for
> watchpoints.
Looks good (just a tiny tiny formatting adjustment - see below).
However, you did not say whether you tested the change (meaning that
you verified that it does not introduce any new failure in the GDB
testsuite), and if you did, on which system. I just want to make
sure the change was properly tested before it is checked in.
> + struct gdb_exception e;
> + TRY_CATCH (e, RETURN_MASK_ALL)
Can you add an empty line between these two line. The style in GDB
is to separate the local variable declarations from the rest of
the code by an empty line.
Thanks,
--
Joel
next prev parent reply other threads:[~2008-12-28 11:48 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
2008-12-26 6:11 ` Joel Brobecker
2008-12-26 7:09 ` Emi SUZUKI
2008-12-28 11:48 ` Joel Brobecker [this message]
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=20081228111719.GC4216@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