From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 31243 invoked by alias); 23 Aug 2002 18:31:42 -0000 Mailing-List: contact gdb-patches-help@sources.redhat.com; run by ezmlm Precedence: bulk List-Subscribe: List-Archive: List-Post: List-Help: , Sender: gdb-patches-owner@sources.redhat.com Received: (qmail 31233 invoked from network); 23 Aug 2002 18:31:41 -0000 Received: from unknown (HELO localhost.redhat.com) (216.138.202.10) by sources.redhat.com with SMTP; 23 Aug 2002 18:31:41 -0000 Received: from ges.redhat.com (localhost [127.0.0.1]) by localhost.redhat.com (Postfix) with ESMTP id 1EBB83ED5; Fri, 23 Aug 2002 14:31:38 -0400 (EDT) Message-ID: <3D667F89.8090603@ges.redhat.com> Date: Fri, 23 Aug 2002 11:34:00 -0000 From: Andrew Cagney User-Agent: Mozilla/5.0 (X11; U; NetBSD macppc; en-US; rv:1.0.0) Gecko/20020810 X-Accept-Language: en-us, en MIME-Version: 1.0 To: Jim Ingham Cc: gdb-patches@sources.redhat.com Subject: Re: [RFC] breakpoints and function prologues... References: Content-Type: text/plain; charset=us-ascii; format=flowed Content-Transfer-Encoding: 7bit X-SW-Source: 2002-08/txt/msg00760.txt.bz2 > > On Thursday, August 22, 2002, at 04:34 PM, gdb-patches-digest-help@sources.redhat.com wrote: > >> The question is, is there a strong reason to change a behavior >> that has been consistent for a very long time (even if undocumented). >> Even if the ability to debug the prologue is un-important for most >> users, it is important to some, and those users (GCC developers, >> for instance) may be quite accustomed to the current behavior. >> I am, for instance... > > The varobj code will fail with file:line number breakpoint setting on the { that starts the function. This is, of course, not a problem for command-line gdb users, but varobj IS a part of gdb... Until we have the CFI stuff well enough set up that, on landing at the beginning of the prologue, the scanner will tell us where the stack frame WILL be when it has been set up so we can record this properly, this will be a problem. Aren't varobj/MI and the CLI separate? varobj/MI could easily request a prologue adjusted breakpoint without modifying the CLI. enjoy, Andrew