From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 3888 invoked by alias); 14 Apr 2005 22:03:19 -0000 Mailing-List: contact gdb-help@sources.redhat.com; run by ezmlm Precedence: bulk List-Subscribe: List-Archive: List-Post: List-Help: , Sender: gdb-owner@sources.redhat.com Received: (qmail 3798 invoked from network); 14 Apr 2005 22:03:12 -0000 Received: from unknown (HELO mail-out4.apple.com) (17.254.13.23) by sourceware.org with SMTP; 14 Apr 2005 22:03:12 -0000 Received: from mailgate2.apple.com (a17-128-100-204.apple.com [17.128.100.204]) by mail-out4.apple.com (8.12.11/8.12.11) with ESMTP id j3EM3Cd8018660 for ; Thu, 14 Apr 2005 15:03:12 -0700 (PDT) Received: from relay3.apple.com (relay3.apple.com) by mailgate2.apple.com (Content Technologies SMTPRS 4.3.17) with ESMTP id ; Thu, 14 Apr 2005 15:03:12 -0700 Received: from [17.219.205.31] ([17.219.205.31]) by relay3.apple.com (8.12.11/8.12.11) with ESMTP id j3EM39dg006365; Thu, 14 Apr 2005 15:03:10 -0700 (PDT) Message-ID: <425EE89D.2020601@apple.com> Date: Thu, 14 Apr 2005 22:03:00 -0000 From: Stan Shebs User-Agent: Mozilla/5.0 (Macintosh; U; PPC Mac OS X Mach-O; en-US; rv:1.7.3) Gecko/20040910 MIME-Version: 1.0 To: Daniel Jacobowitz CC: gdb@sources.redhat.com Subject: Re: Unfinished projects References: <425EBC8F.4030405@apple.com> <20050414190123.GA18019@nevyn.them.org> In-Reply-To: <20050414190123.GA18019@nevyn.them.org> Content-Type: text/plain; charset=us-ascii; format=flowed Content-Transfer-Encoding: 7bit X-SW-Source: 2005-04/txt/msg00082.txt.bz2 Daniel Jacobowitz wrote: >On Thu, Apr 14, 2005 at 11:55:11AM -0700, Stan Shebs wrote: > >>Andrew's sudden departure from GDB maintenance seems to left a >>large number of projects in mid-process; as I'm picking through >>the latest sources trying to figure out how to merge with Apple's >>bits, it's very confusing as to how the new way is supposed to >>work when it's not documented anywhere and there's maybe only >>one example of a configuration using it. >> >>So my question is - what should we do about all these? Are >>some of these intrinsically impossible to complete without >>the right collection of hardware? If so, then maybe we need >>to get tougher about dropping support for some targets, or >>else abandon the projected change. I'd like to work on updating >>the GDB internals manual too, for my own understanding if >>nothing else; should I describe old ways, new ways, or both? >> > >Could you give some specific examples that you're looking at? I've got >no way to answer your questions without more details. For each one, >there's probably someone on the list who knows how it's supposed to >work. > I was being purposefully vague because I wanted to think about general strategy, and because I don't even know how many there are. Specific things I've noticed include async for native, the infptrace vs inf-ptrace situation, and then there's everything with "deprecated" somewhere in the name. So that would be a start - what are all the main incomplete transitions in the code right now? Stan