From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 3804 invoked by alias); 15 Oct 2003 15:02:26 -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 3794 invoked from network); 15 Oct 2003 15:02:24 -0000 Received: from unknown (HELO localhost.redhat.com) (207.219.125.105) by sources.redhat.com with SMTP; 15 Oct 2003 15:02:24 -0000 Received: from redhat.com (localhost [127.0.0.1]) by localhost.redhat.com (Postfix) with ESMTP id D3ED92B89; Wed, 15 Oct 2003 11:02:25 -0400 (EDT) Message-ID: <3F8D6181.6070409@redhat.com> Date: Wed, 15 Oct 2003 15:02:00 -0000 From: Andrew Cagney User-Agent: Mozilla/5.0 (X11; U; NetBSD macppc; en-US; rv:1.0.2) Gecko/20030820 X-Accept-Language: en-us, en MIME-Version: 1.0 To: Michael Snyder Cc: Daniel Jacobowitz , gdb-patches@sources.redhat.com Subject: Re: RFA: Breakpoint infrastructure cleanups [0/8] References: <20031008165534.GA8718@nevyn.them.org> <20031008190502.GA13579@nevyn.them.org> <3F846B04.2070801@redhat.com> <3F85B4AC.7000000@redhat.com> <20031014013831.GB6118@nevyn.them.org> <3F8C18DD.3020508@redhat.com> <20031014155126.GA10669@nevyn.them.org> <3F8C605E.1060604@redhat.com> Content-Type: text/plain; charset=us-ascii; format=flowed Content-Transfer-Encoding: 7bit X-SW-Source: 2003-10/txt/msg00486.txt.bz2 > If this is just an internals issue, then toss a coin, it > doesn't matter. But for the picture that we present to the > user, remember -- we always present a fictional picture that > hides most of the underlying details. The unsophisticated > user thinks he is debugging his code -- not the underlying > machine. If possible, he doesn't want to know eg. that > line seventeen has been broken into several locations and > intermixed with code from 3 other lines. We're sometimes > forced to tell him anyway, but we don't if we can avoid it. Yes, it is user visible (which is why people are also looking for a user-level command, different to "maint info break" and "info break", that displays both the logical and physical breakpoint). With a GUI, I can see each logical breakpoint having an expand widget (correct technical term is?) that lets the user see (modify?) the underlying physical breakpoint list. This is needed, as otherwize something apparently simple "break strcmp" could result in the user unknowingly setting 1000's of breakpoints. enjoy, Andrew