From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 26663 invoked by alias); 28 Apr 2006 18:48:49 -0000 Received: (qmail 26655 invoked by uid 22791); 28 Apr 2006 18:48:49 -0000 X-Spam-Check-By: sourceware.org Received: from nile.gnat.com (HELO nile.gnat.com) (205.232.38.5) by sourceware.org (qpsmtpd/0.31) with ESMTP; Fri, 28 Apr 2006 18:48:47 +0000 Received: from localhost (localhost [127.0.0.1]) by filtered-nile.gnat.com (Postfix) with ESMTP id 225C948CBDF; Fri, 28 Apr 2006 14:48:45 -0400 (EDT) Received: from nile.gnat.com ([127.0.0.1]) by localhost (nile.gnat.com [127.0.0.1]) (amavisd-new, port 10024) with LMTP id 08266-01; Fri, 28 Apr 2006 14:48:44 -0400 (EDT) Received: from takamaka.act-europe.fr (s142-179-108-108.bc.hsia.telus.net [142.179.108.108]) by nile.gnat.com (Postfix) with ESMTP id BEEB148CC0F; Fri, 28 Apr 2006 14:48:44 -0400 (EDT) Received: by takamaka.act-europe.fr (Postfix, from userid 507) id D0F2747E7F; Fri, 28 Apr 2006 11:48:43 -0700 (PDT) Date: Fri, 28 Apr 2006 18:48:00 -0000 From: Joel Brobecker To: Mark Kettenis Cc: jimb@red-bean.com, gdb-patches@sources.redhat.com Subject: Re: [RFC/RFA/i386] pb reading insns if breakpoints still inserted Message-ID: <20060428184843.GG930@adacore.com> References: <20060428171154.GP17613@adacore.com> <8f2776cb0604281054y116acfdavc3649dd8198d80d0@mail.gmail.com> <200604281839.k3SIdfsq030892@elgar.sibelius.xs4all.nl> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <200604281839.k3SIdfsq030892@elgar.sibelius.xs4all.nl> User-Agent: Mutt/1.4i 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-04/txt/msg00372.txt.bz2 > I don't completely disagree with you here, but, a different way to > view the problem is putting the blame with the fact that we (ab)use > the prologue analyzer for skipping the prologue when trying to place a > breakpoint at the start of a function, where we really should be able > to use the debug info for doing this. It would be nice to live in a world when prologue information was always available, but this is not the case, and I think we're very far from it on certain platforms. So I disagree that we abuse the prologue analyzer. Sometimes, we don't have the choice. -- Joel