From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 22007 invoked by alias); 28 May 2007 20:52:08 -0000 Received: (qmail 21999 invoked by uid 22791); 28 May 2007 20:52:07 -0000 X-Spam-Check-By: sourceware.org Received: from nc-71-2-223-254.dyn.embarqhsd.net (HELO localhost.localdomain) (71.2.223.254) by sourceware.org (qpsmtpd/0.31) with ESMTP; Mon, 28 May 2007 20:52:06 +0000 Received: by localhost.localdomain (Postfix, from userid 1000) id B49A617762E; Mon, 28 May 2007 13:52:03 -0700 (PDT) Date: Mon, 28 May 2007 20:52:00 -0000 From: Daniel Jacobowitz To: Ulrich Weigand Cc: Pedro Alves , gdb-patches@sourceware.org, Joel Brobecker Subject: Re: [commit/AIX] Fix error when loading core file Message-ID: <20070528205203.GA911@localhost.localdomain> Mail-Followup-To: Ulrich Weigand , Pedro Alves , gdb-patches@sourceware.org, Joel Brobecker References: <20070521133216.GC1392@caradoc.them.org> <200705282000.l4SK0UbN009109@d12av02.megacenter.de.ibm.com> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <200705282000.l4SK0UbN009109@d12av02.megacenter.de.ibm.com> User-Agent: Mutt/1.5.13 (2006-08-11) X-IsSubscribed: yes Mailing-List: contact gdb-patches-help@sourceware.org; run by ezmlm Precedence: bulk List-Id: List-Subscribe: List-Archive: List-Post: List-Help: , Sender: gdb-patches-owner@sourceware.org X-SW-Source: 2007-05/txt/msg00411.txt.bz2 On Mon, May 28, 2007 at 10:00:30PM +0200, Ulrich Weigand wrote: > Hmmm, I'm not sure how this would work for core files. It looks like > solib-target would work only for targets that provide > to_get_shared_libraries -- are you suggesting to implement that for > the core file target? I guess that would be a gdbarch callback to > implement the AIX-specific handling? Right - that's exactly what I meant. Except that I'm thinking now that I made a mistake; I could have added a target object instead, and then we could use a gdbarch method to implement that target object based on a core file. That's why I haven't followed up on the patch yet; I'm going to try re-working it when I get back from vacation. As to what the contents of the target object should be, I'm not sure. The easiest choice would be the same as the remote protocol format, e.g. "Name:HEXSTR,TextSeg=ADDR;Name:HEXSTR,TextSeg=Addr". The other alternative would be XML in case we think any flexibility would be needed. The nice thing about that is it avoids having to hex-encode the name; we can XML-escape it instead, which is easier in common cases. Now that we have a nicely simple XML parsing infrastructure I like to take advantage of it. -- Daniel Jacobowitz CodeSourcery