From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 21159 invoked by alias); 9 Oct 2003 20:01:50 -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 21152 invoked from network); 9 Oct 2003 20:01:49 -0000 Received: from unknown (HELO mail-out3.apple.com) (17.254.13.22) by sources.redhat.com with SMTP; 9 Oct 2003 20:01:49 -0000 Received: from mailgate1.apple.com (a17-128-100-225.apple.com [17.128.100.225]) by mail-out3.apple.com (8.12.10/8.12.9) with ESMTP id h99K1mvd027276 for ; Thu, 9 Oct 2003 13:01:48 -0700 (PDT) Received: from scv3.apple.com (scv3.apple.com) by mailgate1.apple.com (Content Technologies SMTPRS 4.2.1) with ESMTP id for ; Thu, 9 Oct 2003 13:01:19 -0700 Received: from [17.201.22.245] (inghji6.apple.com [17.201.22.245]) by scv3.apple.com (8.12.9/8.12.9) with ESMTP id h99K1PCn026736 for ; Thu, 9 Oct 2003 13:01:25 -0700 (PDT) Mime-Version: 1.0 (Apple Message framework v606) In-Reply-To: <1065728983.12011.ezmlm@sources.redhat.com> References: <1065728983.12011.ezmlm@sources.redhat.com> Content-Type: text/plain; charset=US-ASCII; format=flowed Message-Id: <73A52B89-FA93-11D7-BB88-000A958F4C44@apple.com> Content-Transfer-Encoding: 7bit From: Jim Ingham Subject: Re: RFA: Breakpoint infrastructure cleanups [0/8] Date: Thu, 09 Oct 2003 20:01:00 -0000 To: gdb-patches@sources.redhat.com X-SW-Source: 2003-10/txt/msg00312.txt.bz2 On Oct 9, 2003, at 12:49 PM, gdb-patches-digest-help@sources.redhat.com wrote: > From: Michael Snyder > Date: October 9, 2003 12:33:14 PM PDT > To: Daniel Jacobowitz > Cc: gdb-patches@sources.redhat.com > Subject: Re: RFA: Breakpoint infrastructure cleanups [0/8] > > > Daniel Jacobowitz wrote: >> On Thu, Oct 09, 2003 at 08:10:46AM +0200, Eli Zaretskii wrote: >>>> Date: Wed, 8 Oct 2003 15:05:02 -0400 >>>> From: Daniel Jacobowitz >>>> >>>>> (gdb) info break >>>>> Num Type Disp Enb Address What >>>>> 1 breakpoint keep y 0x08048354 in foo::foo (in-charge) at >>>>> hello.c:8 >>>>> 0x08048364 in foo::foo (not-in-charge) >>>>> at hello.c:8 >>>>> (gdb) >>>> >>>> Here's the problem that I see. >>>> >>>> For foo::foo, there are two of these things. Having them both in >>>> the >>>> list would be nice. Really nice. >>>> >>>> For inline_accessor_fn there are 3.8 million. In addition to >>>> needing >>>> to do a whole lot of work on GDB internals before we could survive >>>> this >>>> (memory usage; ptrace thrashing inserting and removing them; linked >>>> lists of breakpoints; and that's just the beginning) this has some >>>> severe user interface implications. We don't want to print out all >>>> those addresses by default! >>>> >>>> I'm open to suggestions on how to deal with this. >>> >>> How about a switch to "info break"? By default, show only the >>> in-charge breakpoint, but if the user says "info break -all" or some >>> such, show the other 3.8 million minus one. >>> From a user interface perspective, I got a really strong negative >> pushback the last time I tried to add a switch to any GDB command. > > OK, how about modeling after "info reg" vs. "info all-reg"? > Giving us "info break" and a new "info all-break". > This seems a little odd, because then if I want to see the implementations for one user breakpoint - like where were all the template instantiations for a file:line breakpoint in a C++ template (*) then I say: info all-break 5 Not sure what a better word is but "all" doesn't convey that you want more details about each... Maybe "full" is better, like "info break-full"? Jim (*) Yes, I know that we can't do this yet, but... -- Jim Ingham jingham@apple.com Developer Tools Apple Computer