From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 1914 invoked by alias); 13 Mar 2003 22:20:10 -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 1862 invoked from network); 13 Mar 2003 22:20:10 -0000 Received: from unknown (HELO mail-out1.apple.com) (17.254.0.52) by sources.redhat.com with SMTP; 13 Mar 2003 22:20:10 -0000 Received: from mailgate2.apple.com (A17-129-100-225.apple.com [17.129.100.225]) by mail-out1.apple.com (8.12.8/8.12.8) with ESMTP id h2DMK9Or019156 for ; Thu, 13 Mar 2003 14:20:09 -0800 (PST) Received: from scv2.apple.com (scv2.apple.com) by mailgate2.apple.com (Content Technologies SMTPRS 4.2.1) with ESMTP id for ; Thu, 13 Mar 2003 14:20:09 -0800 Received: from apple.com (inghji.apple.com [17.201.22.240]) by scv2.apple.com (8.11.3/8.11.3) with ESMTP id h2DMK7016948 for ; Thu, 13 Mar 2003 14:20:08 -0800 (PST) Date: Thu, 13 Mar 2003 22:20:00 -0000 Subject: Re: fix break, not add future-break Content-Type: text/plain; charset=US-ASCII; format=flowed Mime-Version: 1.0 (Apple Message framework v551) From: Jim Ingham To: gdb@sources.redhat.com Content-Transfer-Encoding: 7bit In-Reply-To: <1047587818.8256.ezmlm@sources.redhat.com> Message-Id: X-SW-Source: 2003-03/txt/msg00217.txt.bz2 We talked about this a bit here. Jason was worried that users might find getting an extra prompt when they just mistyped annoying. It is certainly a pretty big change in UI, and will be jarring to old hands for a while. On the other hand, I kind of like this better than having to remember to type another command to get shared-library breakpoints to take. Working with programmatic interfaces is different, however. We added a -f flag to -break-insert to turn on the "future" behavior. I think calling it out explicitly like this is better for a programmatic interface, since for a driving program it is better to be able to ask for exactly what you want, than asking for something more general and then having to deal modally with the possible responses to a more general request... Jim On Thursday, March 13, 2003, at 12:36 PM, gdb-digest-help@sources.redhat.com wrote: >> Date: Tue, 11 Mar 2003 10:13:33 -0500 >> From: Andrew Cagney >> >> I'd like to propose that break be modified so that it behaves >> something >> like: >> >> (gdb) break printf.c:printf >> File "printf.c" not currently known, set breakpoint anyway? >> >> And then later: >> >> (gdb) c >> Loading shared library libc.so. >> Enabling breakpoint "printf.c:printf" at .... > > -- Jim Ingham jingham@apple.com Developer Tools Apple Computer