From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 29726 invoked by alias); 25 Aug 2002 14:33:36 -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 29688 invoked from network); 25 Aug 2002 14:33:32 -0000 Received: from unknown (HELO localhost.redhat.com) (24.112.240.27) by sources.redhat.com with SMTP; 25 Aug 2002 14:33:32 -0000 Received: from ges.redhat.com (localhost [127.0.0.1]) by localhost.redhat.com (Postfix) with ESMTP id 5DC143E10; Sun, 25 Aug 2002 10:33:18 -0400 (EDT) Message-ID: <3D68EAAE.8050007@ges.redhat.com> Date: Sun, 25 Aug 2002 07:45:00 -0000 From: Andrew Cagney User-Agent: Mozilla/5.0 (X11; U; NetBSD macppc; en-US; rv:1.0.0) Gecko/20020824 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: <30A3EC98-B7A5-11D6-BB10-000A277A8808@apple.com> Content-Type: text/plain; charset=us-ascii; format=flowed Content-Transfer-Encoding: 7bit X-SW-Source: 2002-08/txt/msg00822.txt.bz2 > Yes, we could change -break-insert to do this. > > It would still break when somebody uses the console to set breakpoints from within Project Builder, however. Like with Insight, we try to support the console as well as we can from PB (we don't do as good a job as Insight, but we are working towards it). We're talking Mac here right? I thought (sarcasm) Mac users did everything using the GUI and AppleScript. > I guess we could go note the breakpoint set event, delete the breakpoint that was just set IF it was set with file:line, and reset it with the "move me past the prologue" cookie. But this seems a bit of a hack. Is your [apple] bug with a GUI user finding that a breakpoint on a function confuses the GUI; or with a GUI user finding that entering the CLI command ``break file.c:10'' confuses the GUI? (A CLI user would have used ``break func'' :-) We've concluded that the former can be fixed without any need to change the CLI. For the latter, the user can still enter ``break *0x1234'' and confuse the GUI. Should GDB ``helpfully'' move that as well? I think the only thing that can be done is ensure that the GUI doesn't get confused (or at least gets confused gracefully :-). For instance, realise that its got a PC in the prologue and display ``incomplete stack frame''. Andrew