From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 15444 invoked by alias); 11 Mar 2003 22:10:34 -0000 Mailing-List: contact gdb-help@sources.redhat.com; run by ezmlm Precedence: bulk List-Subscribe: List-Archive: List-Post: List-Help: , Sender: gdb-owner@sources.redhat.com Received: (qmail 15433 invoked from network); 11 Mar 2003 22:10:31 -0000 Received: from unknown (HELO localhost.redhat.com) (66.30.197.194) by 172.16.49.205 with SMTP; 11 Mar 2003 22:10:31 -0000 Received: from redhat.com (localhost [127.0.0.1]) by localhost.redhat.com (Postfix) with ESMTP id 4881A2B11; Tue, 11 Mar 2003 17:10:30 -0500 (EST) Message-ID: <3E6E5ED6.9040704@redhat.com> Date: Tue, 11 Mar 2003 22:10:00 -0000 From: Andrew Cagney User-Agent: Mozilla/5.0 (X11; U; NetBSD macppc; en-US; rv:1.0.2) Gecko/20030223 X-Accept-Language: en-us, en MIME-Version: 1.0 To: tromey@redhat.com Cc: Gdb List Subject: Re: fix break, not add future-break References: <3E6DFD1D.4090205@redhat.com> <87r89dmxkw.fsf@fleche.redhat.com> Content-Type: text/plain; charset=us-ascii; format=flowed Content-Transfer-Encoding: 7bit X-SW-Source: 2003-03/txt/msg00169.txt.bz2 > "Andrew" == Andrew Cagney writes: > > > Andrew> I'd like to propose that break be modified so that it behaves > Andrew> something like: > Andrew> (gdb) break printf.c:printf > Andrew> File "printf.c" not currently known, set breakpoint anyway? > > For Insight I think it would be useful to have a version of the > command (or a flag, e.g. "break -future") that never asks. I imagine > that's true of other GUIs as well, though you'd have to ask those more > familiar with them. > > The scenario I'm thinking of is saving breakpoints. Right now we save > all the breakpoints in the session. When reloading breakpoints, any > breakpoint that isn't immediately valid is discarded. This is a major > problem for me (and presumably others), since I do a lot of debugging > of code in shared libraries -- meaning that many of my breakpoints are > lost from session to session. Yep. If the breakpoint is comming from a script, just assume `user knows best' and add them regardless. > For breakpoints the user enters by hand, asking seems like a nice > idea. > > Tom Andrew