From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 26961 invoked by alias); 6 Dec 2001 01:39:23 -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 26940 invoked from network); 6 Dec 2001 01:39:22 -0000 Received: from unknown (HELO mail-out2.apple.com) (17.254.0.51) by sources.redhat.com with SMTP; 6 Dec 2001 01:39:22 -0000 Received: from mailgate1.apple.com (A17-128-100-225.apple.com [17.128.100.225]) by mail-out2.apple.com (8.11.3/8.11.3) with ESMTP id fB61dMX19493 for ; Wed, 5 Dec 2001 17:39:22 -0800 (PST) Received: from scv3.apple.com (scv3.apple.com) by mailgate1.apple.com (Content Technologies SMTPRS 4.2.1) with ESMTP id for ; Wed, 5 Dec 2001 17:39:07 -0800 Received: from [17.202.40.220] (inghji.apple.com [17.202.40.220]) by scv3.apple.com (8.11.3/8.11.3) with ESMTP id fB61dL226074 for ; Wed, 5 Dec 2001 17:39:21 -0800 (PST) User-Agent: Microsoft-Entourage/10.0.0.1309 Date: Wed, 05 Dec 2001 17:39:00 -0000 Subject: Re: [RFC] add 'save-breakpoints' command From: Jim Ingham To: GDB Patches Message-ID: In-Reply-To: <1007594419.30359.ezmlm@sources.redhat.com> Mime-version: 1.0 Content-type: text/plain; charset="US-ASCII" Content-transfer-encoding: 7bit X-SW-Source: 2001-12/txt/msg00162.txt.bz2 Project Builder (Apple's IDE which runs on top of gdb) only sets future breakpoints, and Insight could easily do that. The big difference between break and future break is that if you mistype a name in future-break, you won't get an error. You do get some console output telling you that it didn't work, but this is not the same in scripts, for instance. This is a semantic change in how break works, and for that reason I hesitate to just convert break to future break... What do other folks think? Jim > >>>>>> "Klee" == Klee Dienes writes: > > Klee> The 'future-break' command allows one to specify a breakpoint > Klee> that starts off as 'shlib_disabled' instead of generating an > Klee> error if it can't be set immediately. > > Klee> I'm not entirely happy with the future-break command, and > Klee> particularly with its interaction with the save-breakpoints > Klee> mechanism (if you set a breakpoint that is in a shared library > Klee> after shared libraries have been loaded, you have to remember to > Klee> use the future-break command, not the break command). > > Doesn't this mean that programs like Insight would be best advised to > *only* set future breakpoints? In that case let's just add the > functionality directly to the existing breakpoint commands. > > Tom -- +==+==+==+==+==+==+==+==+==+==+==+==+==+==+==+==+==+==+== Jim Ingham jingham@apple.com Developer Tools - gdb