From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 3127 invoked by alias); 17 Mar 2006 22:02:56 -0000 Received: (qmail 3117 invoked by uid 22791); 17 Mar 2006 22:02:55 -0000 X-Spam-Check-By: sourceware.org Received: from e6.ny.us.ibm.com (HELO e6.ny.us.ibm.com) (32.97.182.146) by sourceware.org (qpsmtpd/0.31) with ESMTP; Fri, 17 Mar 2006 22:02:53 +0000 Received: from d01relay04.pok.ibm.com (d01relay04.pok.ibm.com [9.56.227.236]) by e6.ny.us.ibm.com (8.12.11/8.12.11) with ESMTP id k2HM2cwY020463 for ; Fri, 17 Mar 2006 17:02:38 -0500 Received: from d01av04.pok.ibm.com (d01av04.pok.ibm.com [9.56.224.64]) by d01relay04.pok.ibm.com (8.12.10/NCO/VER6.8) with ESMTP id k2HM2Dvj006768 for ; Fri, 17 Mar 2006 17:02:28 -0500 Received: from d01av04.pok.ibm.com (loopback [127.0.0.1]) by d01av04.pok.ibm.com (8.12.11/8.13.3) with ESMTP id k2HM2DQk002297 for ; Fri, 17 Mar 2006 17:02:13 -0500 Received: from dufur.beaverton.ibm.com (dufur.beaverton.ibm.com [9.47.22.20]) by d01av04.pok.ibm.com (8.12.11/8.12.11) with ESMTP id k2HM2CLC001815 for ; Fri, 17 Mar 2006 17:02:12 -0500 Subject: GDB paper accepted for GCC summit From: PAUL GILLIAM Reply-To: pgilliam@us.ibm.com To: gdb@sources.redhat.com Content-Type: text/plain Date: Sat, 18 Mar 2006 11:13:00 -0000 Message-Id: <1142633147.21920.400.camel@dufur.beaverton.ibm.com> Mime-Version: 1.0 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-03/txt/msg00137.txt.bz2 I have not received official word yet, but the following URL strongly suggests that my proposal for a paper at the upcoming gcc summit has been accepted. http://www.gccsummit.org/2006/speakers.php I was afraid that might happen. Here is the abstract: Recent Developments in GDB Many programmers on many platforms depend on GDB to help them find and fix bugs in their programs. Some of these programmers use GDB directly and others indirectly through one of several available graphical front-ends. This paper summarizes major changes in GDB over the last few years, starting with the release of GDB 6.0. These changes were made in a number of areas, including: support for additional architectures; internal changes and reorganizations aimed at better supporting current and future architectures; new features to help programmers debug their programs; and enhancements to make GDB easier to use both for those who use it directly and for those who write and maintain front ends. Also included is an overview of the GDB community and how it operates, touching on a recent overhaul in the way the community interrelates to improve GDB. I would really like to just be the editor and let *you*, the real GDB experts, write it. I think that would be best for the GDB community, and definitely for me 8-). Failing that, I would like suggestions of which developments I should research, using the News file, mailing lists, ChangeLog, and source code as the sources. Either way, I am depending on the GDB community to review the paper and keep me from making a total fool of myself. I will be gone all next week, so *please* send me your ideas, sentences, paragraphs, sections, or heckles so that I can get a running start when I begin work on the paper when I return. -=# Paul Gilliam #=- PS: Here is what I have so far, with out doing any research; depending on my sieve-like memory. New architectures and systems: ???? Internal changes and reorganizations: * New framework for stack unwinding. * More object-oriented ideas. Example: observers. New user features: * Checkpoints. Enhancements: * More robust and useful MI interface. * Support for ADA (or is this a new user feature?) Community reorganization: * Patch champions. As you can see, I have a lot of work to do and I really need your help. (I'm not begging too much, am I?)