From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 2174 invoked by alias); 13 Jan 2006 14:17:29 -0000 Received: (qmail 2166 invoked by uid 22791); 13 Jan 2006 14:17:28 -0000 X-Spam-Check-By: sourceware.org Received: from fra-del-03.spheriq.net (HELO fra-del-03.spheriq.net) (195.46.51.99) by sourceware.org (qpsmtpd/0.31) with ESMTP; Fri, 13 Jan 2006 14:17:26 +0000 Received: from fra-out-03.spheriq.net (fra-out-03.spheriq.net [195.46.51.131]) by fra-del-03.spheriq.net with ESMTP id k0DEHNI2027492 for ; Fri, 13 Jan 2006 14:17:23 GMT Received: from fra-cus-02.spheriq.net (fra-cus-02.spheriq.net [195.46.51.38]) by fra-out-03.spheriq.net with ESMTP id k0DEHNs4018900 for ; Fri, 13 Jan 2006 14:17:23 GMT Received: from beta.dmz-eu.st.com (beta.dmz-eu.st.com [164.129.1.35]) by fra-cus-02.spheriq.net with ESMTP id k0DEHLgg020934 (version=TLSv1/SSLv3 cipher=EDH-RSA-DES-CBC3-SHA bits=168 verify=OK); Fri, 13 Jan 2006 14:17:22 GMT Received: from zeta.dmz-eu.st.com (ns2.st.com [164.129.230.9]) by beta.dmz-eu.st.com (STMicroelectronics) with ESMTP id 2DA3DDA44; Fri, 13 Jan 2006 14:17:16 +0000 (GMT) Received: by zeta.dmz-eu.st.com (STMicroelectronics, from userid 60012) id 2401D4745E; Fri, 13 Jan 2006 14:20:42 +0000 (GMT) Received: from zeta.dmz-eu.st.com (localhost [127.0.0.1]) by zeta.dmz-eu.st.com (STMicroelectronics) with ESMTP id DD5B475994; Fri, 13 Jan 2006 14:20:41 +0000 (UTC) Received: from mail1.bri.st.com (mail1.bri.st.com [164.129.8.218]) by zeta.dmz-eu.st.com (STMicroelectronics) with ESMTP id 210554746E; Fri, 13 Jan 2006 14:20:41 +0000 (GMT) Received: from [164.129.15.13] (terrorhawk.bri.st.com [164.129.15.13]) by mail1.bri.st.com (MOS 3.5.8-GR) with ESMTP id CHD16437 (AUTH stubbsa); Fri, 13 Jan 2006 14:17:13 GMT Message-ID: <43C7B5EF.20900@st.com> Date: Fri, 13 Jan 2006 14:17:00 -0000 From: Andrew STUBBS User-Agent: Thunderbird 1.5 (Windows/20051201) MIME-Version: 1.0 To: Eli Zaretskii Cc: Joel Brobecker , hilfingr@gnat.com, gdb@sourceware.org Subject: Re: [RFC] multiple breakpoints from FILE:LINE References: <20060113104212.0B28848CBD8@nile.gnat.com> <20060113115647.GG10275@adacore.com> In-Reply-To: Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit X-O-Spoofed: Not Scanned X-O-General-Status: No X-O-Spam1-Status: Not Scanned X-O-Spam2-Status: Not Scanned X-O-URL-Status: Not Scanned X-O-Virus1-Status: No X-O-Virus2-Status: Not Scanned X-O-Virus3-Status: No X-O-Virus4-Status: No X-O-Virus5-Status: Not Scanned X-O-Image-Status: Not Scanned X-O-Attach-Status: Not Scanned X-SpheriQ-Ver: 4.2.0 X-IsSubscribed: yes Mailing-List: contact gdb-help@sourceware.org; run by ezmlm Precedence: bulk List-Subscribe: List-Archive: List-Post: List-Help: , Sender: gdb-owner@sourceware.org X-SW-Source: 2006-01/txt/msg00106.txt.bz2 Eli Zaretskii wrote: > How about something like > > break something.adb:12 if SOME_CONDITION > > where SOME_CONDITION is something we should invent to specify the > instance where we want to put the single breakpoint? This has the > advantage of using an existing syntax, especially if the condition > could be made to use some convenience variable. By contrast, what you > suggest modifies the syntax of a location specification; do we really > want that? Not that it makes any real difference but ... To me that looks like it will set a break point everywhere and then check at runtime if it is the right one. Now I know you weren't thinking of doing that, but that's what the condition normally means. It may also make setting a real condition more tricky.