Mirror of the gdb mailing list
 help / color / mirror / Atom feed
From: Daniel Jacobowitz <drow@false.org>
To: Paul Koning <pkoning@equallogic.com>
Cc: jimb@codesourcery.com, eager@eagercon.com,
	stanshebs@earthlink.net, 	gdb@sources.redhat.com
Subject: Re: What's an annex? stratum?
Date: Mon, 25 Jun 2007 19:32:00 -0000	[thread overview]
Message-ID: <20070625193135.GA6391@caradoc.them.org> (raw)
In-Reply-To: <18048.5444.903092.843811@pkoning.equallogic.com>

On Mon, Jun 25, 2007 at 03:19:32PM -0400, Paul Koning wrote:
> That's really unfortunate.  Comments in code are useful but they are
> no substitute for properly written internals documentation.
> 
> By contrast, the internals documentation of GCC seems to be pretty
> helpful and reasonably up to date.

You may have noticed that GCC has approximately ten times as many
active contributors.  Maybe twenty.  It is not twenty times as
complex.  There is no feasible way for the GDB contributors to even
respond to all the incoming bug reports; maintaining internals
documentation of the quality of GCC's would probably require two
contributors' full time effort.

Do you see two spare contributors?  If you do, let me know, please.

> For example: Bug #186 has been troubling us on and off for a long
> time.  I would like to fix it.  But given that this involves going off
> into the deep jungle of the GDB symbol and type machinery, and the
> fact that there is no useable documentation for this stuff, I haven't
> been able to do this.

It's really not as inscrutable as you make it sound, and there are
plenty of people willing to answer questions.  Especially for people
who are interested in fixing bugs and/or improving the documentation.

-- 
Daniel Jacobowitz
CodeSourcery


  reply	other threads:[~2007-06-25 19:32 UTC|newest]

Thread overview: 41+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-06-23 18:01 Michael Eager
2007-06-23 18:57 ` Stan Shebs
2007-06-23 19:08   ` Michael Eager
2007-06-23 19:47     ` Eli Zaretskii
2007-06-23 20:51       ` Michael Eager
2007-06-23 21:23         ` Daniel Jacobowitz
2007-06-23 21:40           ` Michael Eager
2007-06-24  2:58             ` Eli Zaretskii
2007-06-24  4:32               ` Michael Eager
2007-06-25 18:03     ` Jim Blandy
2007-06-25 18:39       ` Michael Eager
2007-06-25 19:10         ` Jim Blandy
2007-06-25 19:26           ` Paul Koning
2007-06-25 19:32             ` Daniel Jacobowitz [this message]
2007-06-25 19:38               ` Robert Dewar
2007-06-25 19:48                 ` Paul Koning
2007-06-25 20:09                   ` Michael Eager
2007-06-25 20:40                     ` Robert Dewar
2007-06-25 20:47                       ` Robert Dewar
2007-06-25 20:31                 ` Eli Zaretskii
2007-06-25 20:44                   ` Robert Dewar
2007-06-25 21:00                     ` Eli Zaretskii
2007-06-25 21:03                       ` Robert Dewar
2007-06-25 21:06                         ` Robert Dewar
2007-06-26 18:34                   ` Markus Deuling
2007-06-26 18:36                     ` Robert Dewar
2007-06-26 21:55                     ` Jim Blandy
2007-06-26 22:14                       ` Nick Roberts
2007-06-26 23:26                       ` Robert Dewar
2007-06-26 23:39                         ` Joel Brobecker
2007-06-26 23:43                           ` Robert Dewar
2007-06-27  0:32                             ` Jim Blandy
2007-06-27  0:42                               ` Robert Dewar
2007-06-27  3:22                                 ` Eli Zaretskii
2007-06-27  0:23                       ` Michael Eager
2007-06-25 20:42             ` Eli Zaretskii
2007-06-25 20:23           ` Eli Zaretskii
2007-06-25 21:52             ` Jim Blandy
2007-06-26  1:04               ` Paul Koning
2007-06-25 20:37         ` Eli Zaretskii
2007-06-25 20:15       ` 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=20070625193135.GA6391@caradoc.them.org \
    --to=drow@false.org \
    --cc=eager@eagercon.com \
    --cc=gdb@sources.redhat.com \
    --cc=jimb@codesourcery.com \
    --cc=pkoning@equallogic.com \
    --cc=stanshebs@earthlink.net \
    /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