From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 11678 invoked by alias); 14 Feb 2006 20:23:00 -0000 Received: (qmail 11669 invoked by uid 22791); 14 Feb 2006 20:22:59 -0000 X-Spam-Check-By: sourceware.org Received: from zproxy.gmail.com (HELO zproxy.gmail.com) (64.233.162.206) by sourceware.org (qpsmtpd/0.31) with ESMTP; Tue, 14 Feb 2006 20:22:57 +0000 Received: by zproxy.gmail.com with SMTP id o37so1434918nzf for ; Tue, 14 Feb 2006 12:22:56 -0800 (PST) Received: by 10.36.25.18 with SMTP id 18mr5401111nzy; Tue, 14 Feb 2006 12:22:55 -0800 (PST) Received: by 10.37.2.63 with HTTP; Tue, 14 Feb 2006 12:22:55 -0800 (PST) Message-ID: <8f2776cb0602141222v24610400s3c8927ff446f185a@mail.gmail.com> Date: Tue, 14 Feb 2006 20:23:00 -0000 From: Jim Blandy To: Mark Kettenis Subject: Re: Fix PR breakpoints/2080 Cc: drow@false.org, gdb-patches@sourceware.org, fnf@specifix.com In-Reply-To: <200602141638.k1EGckea012314@elgar.sibelius.xs4all.nl> MIME-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: quoted-printable Content-Disposition: inline References: <200602141545.k1EFjeGb005665@elgar.sibelius.xs4all.nl> <20060214155232.GA23947@nevyn.them.org> <200602141638.k1EGckea012314@elgar.sibelius.xs4all.nl> X-IsSubscribed: yes 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 X-SW-Source: 2006-02/txt/msg00309.txt.bz2 > > Of course in optimized code we don't expect the prologue skipper to > > work very well, and we use dwarf2 to bypass the prologue analyzer, > > so this may not be a big deal. But I'm somewhat curious to see if > > we could make this extremely sophisticated i386 prologue analyzer > > use Jim's prologue-value.[ch] interface... > > Well, writing that prologue analyzer will be hell of a lot more > difficult for CISC than it is for RISC; even with Jim's > prologue-value.[ch]. Looking at the prologue you put in gdb.arch/i386-prologue.c, I think it'd be okay. The 'and' would set esp to 'unknown', but that should be okay, since the original stack pointer has been saved in ebp. In fact, there's already a pv_logical_and operation in prologue-value.c. If I remember right, s390 prologues can use logical and from time to time.