Mirror of the gdb-patches mailing list
 help / color / mirror / Atom feed
From: Daniel Berlin <dberlin@redhat.com>
To: Eli Zaretskii <eliz@is.elta.co.il>
Cc: gdb-patches@sources.redhat.com
Subject: Re: [PATCH] Start abstraction of C++ abi's
Date: Mon, 19 Feb 2001 06:32:00 -0000	[thread overview]
Message-ID: <x7g0havj4r.fsf@dynamic-addr-83-177.resnet.rochester.edu> (raw)
In-Reply-To: <Pine.SUN.3.91.1010219130212.22360A-100000@is>

Eli Zaretskii <eliz@is.elta.co.il> writes:

> On 19 Feb 2001, Daniel Berlin wrote:
> 
> > But rest assured, this stuff will be documented, unlike the stuff
> > it's replacing.
> 
> Thank you!
> 
> (I'm sorry to be such a nag lately on these matters, but after reading 
> gdbint.texinfo from the first line to the last, I came to the conclusion 
> that it leaves a lot to be desired, to put it gently...)

Yup. Somewhere along the line, the idea that you should be able to
familiarize yourself with an area of gdb by 
1. Reading the approriate section of gdbint
2. Reading the code

got lost, and now we are only left with:

1. Reading the code

which is bad. This gives us no way to know what it's *supposed* to be
doing, or how it's *supposed* to be working, among other things.


Every couple weeks I find some new piece of hardcoded C++ code in gdb
in a random file that I never noticed before.  It was obvious no one
ever tried to document this stuff, or else they would have realized
they file they were trying to put something in was the *wrong one*.

--Dan


  reply	other threads:[~2001-02-19  6:32 UTC|newest]

Thread overview: 19+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2001-02-18 12:51 Daniel Berlin
2001-02-18 22:52 ` Eli Zaretskii
2001-02-19  0:02   ` Daniel Berlin
2001-02-19  3:06     ` Eli Zaretskii
2001-02-19  6:32       ` Daniel Berlin [this message]
2001-02-19  8:48 ` Elena Zannoni
2001-02-19 10:24   ` Daniel Berlin
2001-02-19 11:27 ` Andrew Cagney
2001-02-19 13:17   ` Daniel Berlin
2001-02-19 13:36     ` Andrew Cagney
2001-02-19 14:58     ` Stan Shebs
2001-02-19 15:13     ` Michael Snyder
2001-02-18 16:09 Michael Elizabeth Chastain
2001-02-18 16:51 ` Daniel Berlin
2001-02-18 16:58 Michael Elizabeth Chastain
2001-02-18 18:05 ` Daniel Berlin
     [not found] <200102192211.OAA18590@bosch.cygnus.com>
2001-02-19 14:32 ` Andrew Cagney
2001-02-19 15:01 ` Daniel Berlin
2001-02-19 15:08 Michael Elizabeth Chastain

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=x7g0havj4r.fsf@dynamic-addr-83-177.resnet.rochester.edu \
    --to=dberlin@redhat.com \
    --cc=eliz@is.elta.co.il \
    --cc=gdb-patches@sources.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