From: Mark Kettenis <mark.kettenis@xs4all.nl>
To: drow@false.org
Cc: msnyder@redhat.com, gdb-patches@sourceware.org
Subject: Re: Save the length of inserted breakpoints
Date: Mon, 17 Apr 2006 13:50:00 -0000 [thread overview]
Message-ID: <200604171349.k3HDnTlG026394@elgar.sibelius.xs4all.nl> (raw)
In-Reply-To: <20060417133748.GA15525@nevyn.them.org> (message from Daniel Jacobowitz on Mon, 17 Apr 2006 09:37:48 -0400)
> Date: Mon, 17 Apr 2006 09:37:48 -0400
> From: Daniel Jacobowitz <drow@false.org>
>
> > I still think we should maintain a strict seperation between the
> > high-level breakpoint code and the low-level target code. So I'd
> > really appreciate it if you'd be willing to change your patch such
> > that instead of struct bp_location, you used a different struct, which
> > for now would have three members: the saved contents, the length and
> > the address. It's perfectly ok with me to make that new struct part
> > of struct bp_location to avoid all memory allocation problems.
>
> Sounds perfect! While the argument was a little wearing, I am entirely
> happy with this result. I'll post a patch for this shortly.
Sorry about that. I was a bit annoyed by some of the replies, and I
guess me wanting to make a point here made my subsequent replies a bit
unconstructive.
> I've been thinking about having target methods which don't need the
> shadow contents (there are definitely several) record the "length" of
> the breakpoint as zero; then deprecated_read_memory_nobpt can do the
> right thing. Does this sound reasonable? The alternative is to do an
> unnecessary read from the target.
Absolutely. If the length is zero there are no shadow contents to
worry about. But it is probably better to address
deprecated_read_memory_nobpt in a seperate patch.
Mark
next prev parent reply other threads:[~2006-04-17 13:50 UTC|newest]
Thread overview: 52+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-03-02 22:25 Daniel Jacobowitz
2006-03-02 23:13 ` Mark Kettenis
2006-03-02 23:19 ` Daniel Jacobowitz
2006-03-03 0:08 ` Mark Kettenis
2006-03-03 1:21 ` Daniel Jacobowitz
2006-03-03 13:51 ` Eli Zaretskii
2006-03-03 15:03 ` Daniel Jacobowitz
2006-03-03 17:56 ` Eli Zaretskii
2006-03-03 18:04 ` Daniel Jacobowitz
2006-03-03 22:00 ` Eli Zaretskii
2006-03-03 22:10 ` Daniel Jacobowitz
2006-03-03 22:35 ` Eli Zaretskii
2006-03-03 23:01 ` Daniel Jacobowitz
2006-03-04 10:39 ` Eli Zaretskii
2006-03-04 14:58 ` Daniel Jacobowitz
2006-03-04 15:05 ` Eli Zaretskii
2006-03-04 15:11 ` Daniel Jacobowitz
2006-03-06 19:49 ` Eli Zaretskii
2006-03-07 5:31 ` Michael Snyder
2006-03-04 0:35 ` Steven Johnson
2006-03-04 10:18 ` Daniel Jacobowitz
2006-04-11 21:46 ` Daniel Jacobowitz
2006-04-11 22:32 ` David S. Miller
2006-04-12 7:30 ` Eli Zaretskii
2006-04-12 9:44 ` Mark Kettenis
2006-04-12 12:57 ` Daniel Jacobowitz
2006-04-12 18:38 ` Mark Kettenis
2006-04-12 18:47 ` Daniel Jacobowitz
2006-04-13 8:12 ` Eli Zaretskii
2006-04-13 22:13 ` Mark Kettenis
2006-04-13 22:59 ` Daniel Jacobowitz
2006-04-13 23:30 ` Daniel Jacobowitz
2006-04-14 8:10 ` Eli Zaretskii
2006-04-14 8:52 ` David S. Miller
2006-04-14 8:04 ` Eli Zaretskii
2006-04-14 8:51 ` David S. Miller
2006-04-16 23:58 ` Mark Kettenis
2006-04-17 7:07 ` Eli Zaretskii
2006-04-13 21:57 ` Michael Snyder
2006-04-13 22:59 ` Daniel Jacobowitz
2006-04-16 23:53 ` Mark Kettenis
2006-04-16 23:50 ` Mark Kettenis
2006-04-17 1:41 ` Daniel Jacobowitz
2006-04-17 13:09 ` Mark Kettenis
2006-04-17 13:37 ` Daniel Jacobowitz
2006-04-17 13:50 ` Mark Kettenis [this message]
2006-04-17 19:08 ` Daniel Jacobowitz
2006-04-17 20:25 ` Mark Kettenis
2006-04-17 21:50 ` Daniel Jacobowitz
2006-04-18 8:59 ` Eli Zaretskii
2006-04-18 19:21 ` Daniel Jacobowitz
2006-04-19 7:40 ` Eli Zaretskii
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=200604171349.k3HDnTlG026394@elgar.sibelius.xs4all.nl \
--to=mark.kettenis@xs4all.nl \
--cc=drow@false.org \
--cc=gdb-patches@sourceware.org \
--cc=msnyder@redhat.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