Mirror of the gdb mailing list
 help / color / mirror / Atom feed
From: "Eli Zaretskii" <eliz@gnu.org>
To: "Dave Korn" <dk@artimi.com>
Cc: cagney@gnu.org, gdb@sources.redhat.com
Subject: Re: Discussion: Formalizing the deprecation process in GDB
Date: Fri, 08 Oct 2004 19:16:00 -0000	[thread overview]
Message-ID: <01c4ad54$Blat.v2.2.2$5fc635a0@zahav.net.il> (raw)
In-Reply-To: <NUTMEG7sFoai8XKPl5G0000032c@NUTMEG.CAM.ARTIMI.COM> (dk@artimi.com)

> From: "Dave Korn" <dk@artimi.com>
> Cc: <cagney@gnu.org>,
> 	<gdb@sources.redhat.com>
> Date: Fri, 8 Oct 2004 14:30:36 +0100
> 
> 3.3 Single Stepping 
> 3.4 Signal Handling 
> 3.5 Thread Handling 
> 3.6 Inferior Function Calls
> 
> [ Section 4 User Interface ]
> 
> 4.3 Console Printing 
> 4.4 TUI
> 
> [ Section 9 Target Architecture Definition ]
> 
> 9.7 Frame Interpretation 
> 9.8 Inferior Call Setup
> 9.9 Compiler Characteristics
> 
> [ Section 10 Target Vector Definition ]
> 
> 10.3 ROM Monitor Interface 
> 10.4 Custom Protocols
> 10.5 Transport Layer
> 
> [ Section 11 Native Debugging ]
> 
> 11.2 ptrace
> 11.3 /proc
> 11.4 win32
> 11.5 shared libraries
> 
> [ Section 12 Support Libraries ]
> 12.3 readline 
> 12.4 mmalloc
> 
> 12.7 include

Thanks for the footwork.

Yes, these are the empty sections, sigh.  They await volunteers to
document the related features.

The one for readline could use part of the Readline's docs, though.  I
will try to make that happen.


  parent reply	other threads:[~2004-10-08 16:34 UTC|newest]

Thread overview: 32+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2004-09-27 17:55 Joel Brobecker
2004-09-27 20:35 ` Eli Zaretskii
2004-10-06  6:14 ` Andrew Cagney
2004-10-06 13:39   ` Eli Zaretskii
2004-10-07  4:48     ` Joel Brobecker
2004-10-07 14:27       ` Dave Korn
2004-10-07 15:12         ` Joel Brobecker
2004-10-07 16:16           ` Andrew Cagney
2004-10-07 18:50             ` Dave Korn
2004-10-07 16:14         ` Andrew Cagney
2004-10-07 18:08           ` Dave Korn
2004-10-07 19:18             ` Joel Brobecker
2004-10-07 19:28               ` Dave Korn
2004-10-08  7:08                 ` Joel Brobecker
2004-10-08 12:13                   ` Eli Zaretskii
2004-10-08 12:05               ` Eli Zaretskii
2004-10-08  8:54             ` Fabian Cenedese
2004-10-08 11:45           ` Eli Zaretskii
2004-10-08 19:22             ` Andrew Cagney
2004-10-10 21:31               ` Eli Zaretskii
2004-10-08 10:45         ` Eli Zaretskii
2004-10-08 13:31           ` Dave Korn
2004-10-08 13:38             ` Eli Zaretskii
2004-10-08 13:43               ` Dave Korn
2004-10-08 13:44                 ` Dave Korn
2004-10-08 19:16                 ` Eli Zaretskii [this message]
2004-10-08 19:45                   ` Eli Zaretskii
2004-10-08 22:10             ` Andrew Cagney
2004-10-08 10:38       ` Eli Zaretskii
2004-10-11 15:11     ` Andrew Cagney
2004-10-12  7:34       ` Eli Zaretskii
2004-10-12 13:42         ` Mark Kettenis

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='01c4ad54$Blat.v2.2.2$5fc635a0@zahav.net.il' \
    --to=eliz@gnu.org \
    --cc=cagney@gnu.org \
    --cc=dk@artimi.com \
    --cc=gdb@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