From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 19729 invoked by alias); 27 Jul 2011 12:32:07 -0000 Received: (qmail 19721 invoked by uid 22791); 27 Jul 2011 12:32:07 -0000 X-SWARE-Spam-Status: No, hits=-2.3 required=5.0 tests=AWL,BAYES_00,DKIM_SIGNED,DKIM_VALID,DKIM_VALID_AU,FREEMAIL_FROM,RCVD_IN_DNSWL_LOW X-Spam-Check-By: sourceware.org Received: from mail-yx0-f169.google.com (HELO mail-yx0-f169.google.com) (209.85.213.169) by sourceware.org (qpsmtpd/0.43rc1) with ESMTP; Wed, 27 Jul 2011 12:31:52 +0000 Received: by yxn22 with SMTP id 22so821114yxn.0 for ; Wed, 27 Jul 2011 05:31:52 -0700 (PDT) MIME-Version: 1.0 Received: by 10.236.35.165 with SMTP id u25mr8418191yha.188.1311769911980; Wed, 27 Jul 2011 05:31:51 -0700 (PDT) Received: by 10.236.109.131 with HTTP; Wed, 27 Jul 2011 05:31:51 -0700 (PDT) In-Reply-To: References: <20110505162855.GA2546@adacore.com> <83bozgmhil.fsf@gnu.org> <83k4dcd1bh.fsf@gnu.org> Date: Wed, 27 Jul 2011 15:10:00 -0000 Message-ID: Subject: Re: [RFC] canonical linespec and multiple breakpoints ... From: Matt Rice To: Tom Tromey Cc: gdb-patches@sourceware.org Content-Type: text/plain; charset=ISO-8859-1 X-IsSubscribed: yes Mailing-List: contact gdb-patches-help@sourceware.org; run by ezmlm Precedence: bulk List-Id: List-Subscribe: List-Archive: List-Post: List-Help: , Sender: gdb-patches-owner@sourceware.org X-SW-Source: 2011-07/txt/msg00760.txt.bz2 On Tue, Jul 26, 2011 at 12:53 PM, Tom Tromey wrote: > > I am not completely sold on this, but I wanted to float the idea for > comments. I guess, a case where this one acts oddly is, there is a currently unambiguously resolvable function, which will become ambiguous on future shared library processing. in that case you need a way to force a pending breakpoint. also because outside of dlopen there is generally no prompt in between shared library processing, usage of a 'permanent pending breakpoint' will cause debug-info for all shared libraries to be processed in between run and the gdb prompt. it doesn't seem like it is incompatible with foo.so:function_of_doom style breakpoints that could be used to mitigate the chewing through all debug-info too. it doesn't gracefully/effortlessly handle ambiguous breakpoints like the previous solution, but to me that isn't that big of an issue, as long as there is a way to handle them when they are encountered. That there is some way to resolve an ambiguous location to the one I want gdb to stop at, rather than that it manages to resolve all ambiguous linespecs. Shrug.