Mirror of the gdb mailing list
 help / color / mirror / Atom feed
From: Nick Roberts <nickrob@snap.net.nz>
To: Jim Blandy <jimb@codesourcery.com>
Cc: Markus Deuling <deuling@de.ibm.com>,
		Eli Zaretskii <eliz@gnu.org>, Robert Dewar <dewar@adacore.com>,
		pkoning@equallogic.com, eager@eagercon.com,
	stanshebs@earthlink.net, 	gdb@sources.redhat.com
Subject: Re: What's an annex? stratum?
Date: Tue, 26 Jun 2007 22:14:00 -0000	[thread overview]
Message-ID: <18049.36769.426400.963565@kahikatea.snap.net.nz> (raw)
In-Reply-To: <m3645av0rf.fsf@codesourcery.com>

 > At the moment, GDB:
 > 
 > - can't print a C++ map<string, string> value in any reasonable form,
 >   or even a vector<int>, or carry out many other essential C++
 >   operations,
 > 
 > - can't debug multiple processes at the same time,
 > 
 > - is slow to start up on large programs, and uses a lot of memory,
 > 
 > - can't let other threads continue to run while one is stopped,
 > 
 > - can't be scripted in a reasonable language,
 > 
 > - or do many other things we all could think of.

This looks like another list that could be added to the wiki that Daniel has
created.

 > ...
 > I want to hear an internals documentation advocate say, "I'm going to
 > work on the internals documentation because I think the date at which
 > user-visible project X is complete will move closer when I do so."

I agree.  I also would like to see a self contained internals manual but I
think it's churlish to expect someone else to write it for me.  Emacs has
no such manual, at all.

-- 
Nick                                           http://www.inet.net.nz/~nickrob


  reply	other threads:[~2007-06-26 22:14 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
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 [this message]
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=18049.36769.426400.963565@kahikatea.snap.net.nz \
    --to=nickrob@snap.net.nz \
    --cc=deuling@de.ibm.com \
    --cc=dewar@adacore.com \
    --cc=eager@eagercon.com \
    --cc=eliz@gnu.org \
    --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