From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 1161 invoked by alias); 13 Nov 2005 18:19:15 -0000 Mailing-List: contact gdb-patches-help@sourceware.org; run by ezmlm Precedence: bulk List-Subscribe: List-Archive: List-Post: List-Help: , Sender: gdb-patches-owner@sourceware.org Received: (qmail 892 invoked by uid 22791); 13 Nov 2005 18:19:12 -0000 Received: from nevyn.them.org (HELO nevyn.them.org) (66.93.172.17) by sourceware.org (qpsmtpd/0.30-dev) with ESMTP; Sun, 13 Nov 2005 18:19:12 +0000 Received: from drow by nevyn.them.org with local (Exim 4.54) id 1EbMRZ-0000yz-Ae; Sun, 13 Nov 2005 13:19:09 -0500 Date: Sun, 13 Nov 2005 18:28:00 -0000 From: Daniel Jacobowitz To: Joel Brobecker Cc: Randolph Chung , Jim Blandy , gdb-patches@sources.redhat.com Subject: Re: [hppa] FYI: confusion in unwind descriptor field meaning Message-ID: <20051113181909.GB3599@nevyn.them.org> Mail-Followup-To: Joel Brobecker , Randolph Chung , Jim Blandy , gdb-patches@sources.redhat.com References: <20051109203108.GX1635@adacore.com> <43735815.3070805@tausq.org> <20051111001017.GJ1635@adacore.com> <437548AF.5090107@tausq.org> <8f2776cb0511111838m64d478d9s2e04db338fbf7fc8@mail.gmail.com> <4375624D.1070202@tausq.org> <8f2776cb0511112022k746e7909r24be2e964dd45a13@mail.gmail.com> <437571F4.8020508@tausq.org> <20051112060426.GT1635@adacore.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <20051112060426.GT1635@adacore.com> User-Agent: Mutt/1.5.8i X-SW-Source: 2005-11/txt/msg00169.txt.bz2 On Fri, Nov 11, 2005 at 10:04:26PM -0800, Joel Brobecker wrote: > I think this begs for an experiment, which I hope I'll be able to make > sometime during the winter. I can start with the code we have, since > we already have a lot of code that analyzes the prologue, and see how > to reconstitute the information we would otherwise get from the unwind > record. If you're going to do this, I recommend using the prologue analysis framework Jim posted, which hopefully we'll have merged by then. If we haven't, well, an active user of it will make it easier. > Randolph I think raised a very good point regarding the computation > of the end of the prologue, though. I don't know if we can determine > this without the help of the unwind record. For this, I don't have > enough experience with that chip. A good prologue analyzer may just want to go until it sees something confusing. Depending on the peculiarities of the architecture, this may be enough. -- Daniel Jacobowitz CodeSourcery, LLC