From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 14177 invoked by alias); 15 May 2006 17:55:34 -0000 Received: (qmail 14169 invoked by uid 22791); 15 May 2006 17:55:33 -0000 X-Spam-Check-By: sourceware.org Received: from e33.co.us.ibm.com (HELO e33.co.us.ibm.com) (32.97.110.151) by sourceware.org (qpsmtpd/0.31) with ESMTP; Mon, 15 May 2006 17:55:31 +0000 Received: from westrelay02.boulder.ibm.com (westrelay02.boulder.ibm.com [9.17.195.11]) by e33.co.us.ibm.com (8.12.11.20060308/8.12.11) with ESMTP id k4FHtSeW024534 for ; Mon, 15 May 2006 13:55:29 -0400 Received: from d03av02.boulder.ibm.com (d03av02.boulder.ibm.com [9.17.195.168]) by westrelay02.boulder.ibm.com (8.12.10/NCO/VER6.8) with ESMTP id k4FHtSr2268932 for ; Mon, 15 May 2006 11:55:28 -0600 Received: from d03av02.boulder.ibm.com (loopback [127.0.0.1]) by d03av02.boulder.ibm.com (8.12.11/8.13.3) with ESMTP id k4FHtS9w024047 for ; Mon, 15 May 2006 11:55:28 -0600 Received: from dufur.beaverton.ibm.com (dufur.beaverton.ibm.com [9.47.22.20]) by d03av02.boulder.ibm.com (8.12.11/8.12.11) with ESMTP id k4FHtRP3023979; Mon, 15 May 2006 11:55:28 -0600 Subject: Re: TODO List? From: PAUL GILLIAM Reply-To: pgilliam@us.ibm.com To: Rob Quill Cc: gdb@sourceware.org In-Reply-To: References: <20060513154940.GB5022@nevyn.them.org> Content-Type: text/plain Date: Mon, 15 May 2006 18:41:00 -0000 Message-Id: <1147711905.3672.144.camel@dufur.beaverton.ibm.com> Mime-Version: 1.0 X-Mailer: Evolution 2.2.2 (2.2.2-5) Content-Transfer-Encoding: 7bit X-IsSubscribed: yes Mailing-List: contact gdb-help@sourceware.org; run by ezmlm Precedence: bulk List-Subscribe: List-Archive: List-Post: List-Help: , Sender: gdb-owner@sourceware.org X-SW-Source: 2006-05/txt/msg00209.txt.bz2 > I have downloaded the GDB Internals document, and will be having > a look through that. Do you have any other suggestions for how to go > about getting to grips with the code? Also, is it alright to ask > questions about the GDB Internals document on here, if there are > things I don't understand. > It might be really cool to use the internals document as a way of keeping track of your developing understanding. What I mean by that: If you have a question about something that is covered in the internals document and have a dialog with the gdb@ list about it, formalize your new understanding by making needed changes in the document and running them through the gdb-patches@ list. This would only apply if your original lack of understanding was due to a faulty section or poor wording, etc. in the internals document. If your question is about something that is *not* covered in the document, but maybe should be, then update the document such that your question is now answered by it. If you could somehow incorporate this kind of procedure into your project goals, then you would get credit for the 'extra' work entailed, as well as the satisfaction of knowing you have helped others down the line. There are, of course, problems with this idea. For example, the level of detail in a question my not be appropriate for the internals document, especially if in an area of GDB that is undergoing a lot of change. For many of us, the problem with this idea is the pressure we have to 'fix the next bug and get it on to the next one'. Kind of a 'what have you done for me lately' kind of thing. But maybe in your environment, this might not apply. Anyway, it's just a thought. -=# Paul Gilliam #=-