From: Eli Zaretskii <eliz@gnu.org>
To: Mark Kettenis <mark.kettenis@xs4all.nl>
Cc: gdb-patches@sourceware.org
Subject: Re: Save the length of inserted breakpoints
Date: Fri, 14 Apr 2006 08:10:00 -0000 [thread overview]
Message-ID: <ubqv437d1.fsf@gnu.org> (raw)
In-Reply-To: <20060413225917.GA30759@nevyn.them.org> (message from Daniel Jacobowitz on Thu, 13 Apr 2006 18:59:17 -0400)
> Date: Thu, 13 Apr 2006 18:59:17 -0400
> From: Daniel Jacobowitz <drow@false.org>
> Cc: eliz@gnu.org, gdb-patches@sourceware.org
>
> I'm way tired of discussing this patch, however. I'd like to remind
> the audience that I'm not trying to clean up the target breakpoint
> interface; I was trying to fix a nasty debugging problem for ARM
> where it's perfectly obvious to the user what mode some code is in,
> but GDB gets lost. My first version was too limited to the problem
> case and was dismissed as hopelessly ugly. So I cleaned it up,
> added some abstraction, and now it's "obfuscated". Every time I
> have to overhaul an interface to fix a bug, I get a little bit
> more frustrated. The bug took an hour, and this has taken days.
And therein lies the real problem.
Mark, is your objection really so serious as to leave this bug
unfixed rather than fixed as Daniel suggested?
If it is, I'd like to hear opinions of others; if you are the only one
who objects, I'd recommend to commit the patch over your objections.
next prev parent reply other threads:[~2006-04-14 8:10 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 [this message]
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=ubqv437d1.fsf@gnu.org \
--to=eliz@gnu.org \
--cc=gdb-patches@sourceware.org \
--cc=mark.kettenis@xs4all.nl \
/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