From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 17620 invoked by alias); 4 Feb 2008 04:08:59 -0000 Received: (qmail 17611 invoked by uid 22791); 4 Feb 2008 04:08:59 -0000 X-Spam-Check-By: sourceware.org Received: from romy.inter.net.il (HELO romy.inter.net.il) (213.8.233.24) by sourceware.org (qpsmtpd/0.31) with ESMTP; Mon, 04 Feb 2008 04:08:39 +0000 Received: from HOME-C4E4A596F7 (IGLD-80-230-68-135.inter.net.il [80.230.68.135]) by romy.inter.net.il (MOS 3.7.3-GA) with ESMTP id KCR91617 (AUTH halo1); Mon, 4 Feb 2008 06:08:18 +0200 (IST) Date: Mon, 04 Feb 2008 04:08:00 -0000 Message-Id: From: Eli Zaretskii To: Joel Brobecker CC: gdb-patches@sourceware.org In-reply-to: <20080203204000.GB21614@adacore.com> (message from Joel Brobecker on Sun, 3 Feb 2008 12:40:00 -0800) Subject: Re: [RFA] new set/show multiple-choice-auto-select command (take 3) Reply-to: Eli Zaretskii References: <20080203043755.GI1581@adacore.com> <20080203204000.GB21614@adacore.com> 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: 2008-02/txt/msg00063.txt.bz2 > Date: Sun, 3 Feb 2008 12:40:00 -0800 > From: Joel Brobecker > Cc: gdb-patches@sourceware.org > > > > The change since the last time is that the default had been changed > > > to "all". > > > > Is this the current behavior, or are we changing the behavior here? > > It's kind of both :). If you remember some work has been done recently > to handle breakpoints with multiple locations. For instance, breaking > on a constructor results in at least 2 locations for the same > breakpoint. In that case, the behavior was the equivalent of having > the new setting set to "all", so we're not changing anything here. > > But when dealing with homonyms (for instance, breaking on overloaded > methods), the standard behavior was to ask the user to select the ones > he wanted to break on. This patch makes things more consistent by > changing the behavior. I'm uneasy about changing the default behavior, but perhaps this is okay if breaking on overloaded methods was introduced not too long ago. Is that the case? In any case, the NEWS entry should mention this change in the default.