RE: Discussion: Formalizing the deprecation process in GDB

["Dave Korn" <dk@artimi.com>]

> -----Original Message-----
> From: halo1 On Behalf Of Eli Zaretskii
> Sent: 08 October 2004 14:13

> >   However, since we mention it, sections 3.3-3.6, 4.3-4.4, 9.7-9.9,
> > 10.3-10.6, 11.2-11.5, 12.3-12.4 and 12.7 of gdbint are missing.
> 
> Just so it is easier for me to find those places, could you please
> tell the names of these sections, instead of just numbers?

  Certainly can:

[ Section 3 Algorithms ]

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


  :)  As you see, there are some fairly fundamental gdb-internals there that
could really do with a bit of explaining.  Things like "Frame
interpretation" and "Inferior call setup" are IMO among the most basic and
important aspects of gdb<->target interaction that a newbie approaching the
code really needs to have a clear understanding of.

> I agree that such ``documentation'' is very unhelpful.  Would someone
> please volunteer to write something more useful?

  I find myself in something of a catch-22: I'd love to offer to write some
docs, but in order to do so I'd need to understand the underlying gdb
mechanics much better, and in order to do that, I feel that I'd need.....
some docs!  

  I actually had to put aside the in-house gdb I was working on a while back
as other priorities came up.  If nobody's gotten down to this as/when I get
back to it, I guess I'll try and keep some notes as I go along trying to
work it all out from the code that might be able to serve as a starting
point.  However, I have 'issues' with my assign paperwork at the moment that
mean this could be some way off in the future.....

    cheers, 
      DaveK
-- 
Can't think of a witty .sigline today....