From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 15923 invoked by alias); 8 Oct 2003 20:55:39 -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 15905 invoked from network); 8 Oct 2003 20:55:39 -0000 Received: from unknown (HELO mx1.redhat.com) (66.187.233.31) by sources.redhat.com with SMTP; 8 Oct 2003 20:55:39 -0000 Received: from int-mx1.corp.redhat.com (int-mx1.corp.redhat.com [172.16.52.254]) by mx1.redhat.com (8.11.6/8.11.6) with ESMTP id h98KtbM02203 for ; Wed, 8 Oct 2003 16:55:37 -0400 Received: from pobox.corp.redhat.com (pobox.corp.redhat.com [172.16.52.156]) by int-mx1.corp.redhat.com (8.11.6/8.11.6) with ESMTP id h98Ktbc23240; Wed, 8 Oct 2003 16:55:37 -0400 Received: from localhost.redhat.com (devserv.devel.redhat.com [172.16.58.1]) by pobox.corp.redhat.com (8.12.8/8.12.8) with ESMTP id h98KtadT015863; Wed, 8 Oct 2003 16:55:37 -0400 Received: by localhost.redhat.com (Postfix, from userid 469) id 44B682CCB3; Wed, 8 Oct 2003 17:06:35 -0400 (EDT) From: Elena Zannoni MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Message-ID: <16260.31835.64460.668846@localhost.redhat.com> Date: Wed, 08 Oct 2003 20:55:00 -0000 To: Daniel Jacobowitz Cc: Jim Blandy , gdb-patches@sources.redhat.com, Michael Snyder Subject: Re: RFA: Breakpoint infrastructure cleanups [0/8] In-Reply-To: <20031008190502.GA13579@nevyn.them.org> References: <20031008165534.GA8718@nevyn.them.org> <20031008190502.GA13579@nevyn.them.org> X-SW-Source: 2003-10/txt/msg00261.txt.bz2 Daniel Jacobowitz writes: > > I think 'info break' should list the addresses. I don't know how this > > should fit into the MI format, but it ought to be MI that changes, > > rather than omitting useful behavior. > > > > In my ideal world, you'd get an explanation for why each address was > > chosen, when it's not obvious: > > > > (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. > There is already 'maint info break', how about extending that? Would you be able to distinguish between foo::foo breakpoints and inline breakpoints so that they can be displayed on separate lists/commands? elena > -- > Daniel Jacobowitz > MontaVista Software Debian GNU/Linux Developer