From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 5812 invoked by alias); 11 Jun 2003 12:02: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 5669 invoked from network); 11 Jun 2003 12:02:16 -0000 Received: from unknown (HELO mx1.redhat.com) (66.187.233.31) by sources.redhat.com with SMTP; 11 Jun 2003 12:02:16 -0000 Received: from int-mx2.corp.redhat.com (nat-pool-rdu-dmz.redhat.com [172.16.52.200] (may be forged)) by mx1.redhat.com (8.11.6/8.11.6) with ESMTP id h5BC2GH22864 for ; Wed, 11 Jun 2003 08:02:16 -0400 Received: from potter.sfbay.redhat.com (potter.sfbay.redhat.com [172.16.27.15]) by int-mx2.corp.redhat.com (8.11.6/8.11.6) with ESMTP id h5BC2FT29760 for ; Wed, 11 Jun 2003 08:02:15 -0400 Received: from cygbert.vinschen.de (vpn50-1.rdu.redhat.com [172.16.50.1]) by potter.sfbay.redhat.com (8.11.6/8.11.6) with ESMTP id h5BC2Ew03855 for ; Wed, 11 Jun 2003 05:02:14 -0700 Received: by cygbert.vinschen.de (Postfix, from userid 500) id 486A55811F; Wed, 11 Jun 2003 14:02:12 +0200 (CEST) Date: Wed, 11 Jun 2003 12:02:00 -0000 From: Corinna Vinschen To: gdb@sources.redhat.com Subject: HOWTO move a target from old style multiarched to new style multiarched? Message-ID: <20030611120212.GB30116@cygbert.vinschen.de> Reply-To: gdb@sources.redhat.com Mail-Followup-To: gdb@sources.redhat.com Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.4.1i X-SW-Source: 2003-06/txt/msg00180.txt.bz2 Hi, there were a lot of changes in the last couple of months to convert gdb to a new way of doing things. That's probably good but I don't know how many people actually understand the whole process. I must admit, I don't. I'm under the impression the documentation is missing an important part. There's some sort of description spread over the source code now but it doesn't give a coherent picture and I also didn't find that in the docs. Wouldn't it be possible to write a HOWTO for the poor developer soul, who's left behind with a target with now using 80% deprecated functions? IMHO, that HOWTO written by somebody who knows what's going on could tells us The datastructure `struct bits' is replaced by `struct pieces'. This requires to use a new set of functions... Create functions foo(), bar() and baz(), doing... If you use function new_and_shiny() you must also replace old_and_dirty(), otherwise... The functions old() and cruft() are replaced by glitter() which returns yadda... Function ugly() is not used anymore and can be removed without substitution... and so on. That would be very helpful and probably speed up the conversion of targets to "new style" enormously. Or did I just miss the documentation on this? Corinna -- Corinna Vinschen Cygwin Developer Red Hat, Inc. mailto:vinschen@redhat.com