From: Eli Zaretskii <eliz@gnu.org>
To: gdb-patches@sourceware.org
Subject: Re: Save the length of inserted breakpoints
Date: Fri, 03 Mar 2006 22:35:00 -0000 [thread overview]
Message-ID: <uoe0n2noj.fsf@gnu.org> (raw)
In-Reply-To: <20060303214359.GA20872@nevyn.them.org> (message from Daniel Jacobowitz on Fri, 3 Mar 2006 16:43:59 -0500)
> Date: Fri, 3 Mar 2006 16:43:59 -0500
> From: Daniel Jacobowitz <drow@false.org>
>
> Do you believe it _should_ be the target vector's responsibility to
> remember inserted breakpoint details?
For details that are specific to a target, yes, I think so.
> I find this a little bit strange, since every target will have to do
> just about the same thing.
We could have a generic method that most of them could use. Those
that have peculiarities, such as those which started this thread, will
have to provide their own methods.
next prev parent reply other threads:[~2006-03-03 22:00 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 [this message]
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
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=uoe0n2noj.fsf@gnu.org \
--to=eliz@gnu.org \
--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