From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 30588 invoked by alias); 1 Jul 2003 00:14:03 -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 30581 invoked from network); 1 Jul 2003 00:14:02 -0000 Received: from unknown (HELO mx1.redhat.com) (66.187.233.31) by sources.redhat.com with SMTP; 1 Jul 2003 00:14:02 -0000 Received: from int-mx1.corp.redhat.com (int-mx1.corp.redhat.com [172.16.52.254]) by mx1.redhat.com (8.11.6/8.11.6) with ESMTP id h610E2H04378 for ; Mon, 30 Jun 2003 20:14:02 -0400 Received: from pobox.corp.redhat.com (pobox.corp.redhat.com [172.16.52.156]) by int-mx1.corp.redhat.com (8.11.6/8.11.6) with ESMTP id h610E2I30922 for ; Mon, 30 Jun 2003 20:14:02 -0400 Received: from localhost.redhat.com (romulus-int.sfbay.redhat.com [172.16.27.46]) by pobox.corp.redhat.com (8.11.6/8.11.6) with ESMTP id h610DvE14130; Mon, 30 Jun 2003 20:13:57 -0400 Received: by localhost.redhat.com (Postfix, from userid 469) id 11FAE2CAB2; Mon, 30 Jun 2003 20:20:47 -0400 (EDT) From: Elena Zannoni MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Message-ID: <16128.54238.846514.981630@localhost.redhat.com> Date: Tue, 01 Jul 2003 00:14:00 -0000 To: Kevin Buettner Cc: Jim Blandy , gdb@sources.redhat.com Subject: Re: IBM S/390 prologue analysis revisited In-Reply-To: <1030630233621.ZM27669@localhost.localdomain> References: <1030630233621.ZM27669@localhost.localdomain> X-SW-Source: 2003-07/txt/msg00000.txt.bz2 Kevin Buettner writes: > On Jun 30, 6:22pm, Jim Blandy wrote: > > > So, how do you folks feel the balance falls? > > I'd like to see your patch go in, if for no other reason than that > it'll help provide better backtraces for executables which lack > debugging information. (DWARF CFI won't always be available, > will it?) > yeah, I agree. > Also, I happen to think that the implementation is pretty cool and I > think it'd be worth having around as a good example of how to > implement a prologue analyzer. > yes, please elena > Kevin