From: Daniel Jacobowitz <drow@false.org>
To: Eli Zaretskii <eliz@gnu.org>
Cc: gdb-patches@sourceware.org
Subject: Re: GDB to C++ issue: deletion
Date: Fri, 01 Aug 2008 12:51:00 -0000 [thread overview]
Message-ID: <20080801125124.GA13594@caradoc.them.org> (raw)
In-Reply-To: <u8wvhnjsb.fsf@gnu.org>
On Fri, Aug 01, 2008 at 12:53:24PM +0300, Eli Zaretskii wrote:
> Still, I think that it is a misrepresentation to say that GDB code
> cannot be understood by "mere mortals". Most problems, as far as I
> remember from questions posted here, are about the high-level
> architectural aspects, asked by those who want to add support for some
> novel or unusual platform. People who need to fix a bug in existing
> code normally don't have much trouble understanding it.
For what it's worth, that's not my experience at all. Contributors
have a lot of trouble with the GDB code. One of the biggest problems
is cleanups, which is one reason I'm listening with interest to this
conversation.
--
Daniel Jacobowitz
CodeSourcery
next parent reply other threads:[~2008-08-01 12:51 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <200807312204.m6VM4JQM007611@tully.CS.Berkeley.EDU>
[not found] ` <200808011054.24219.apoenitz@trolltech.com>
[not found] ` <u8wvhnjsb.fsf@gnu.org>
2008-08-01 12:51 ` Daniel Jacobowitz [this message]
2008-08-01 13:34 ` 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=20080801125124.GA13594@caradoc.them.org \
--to=drow@false.org \
--cc=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