From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 516 invoked by alias); 9 Nov 2002 22:38:55 -0000 Mailing-List: contact gdb-help@sources.redhat.com; run by ezmlm Precedence: bulk List-Subscribe: List-Archive: List-Post: List-Help: , Sender: gdb-owner@sources.redhat.com Received: (qmail 507 invoked from network); 9 Nov 2002 22:38:55 -0000 Received: from unknown (HELO crack.them.org) (65.125.64.184) by sources.redhat.com with SMTP; 9 Nov 2002 22:38:55 -0000 Received: from nevyn.them.org ([66.93.61.169] ident=mail) by crack.them.org with asmtp (Exim 3.12 #1 (Debian)) id 18Ag89-0001HX-00; Sat, 09 Nov 2002 18:39:13 -0600 Received: from drow by nevyn.them.org with local (Exim 3.36 #1 (Debian)) id 18AeGk-0008Dk-00; Sat, 09 Nov 2002 17:39:58 -0500 Date: Sat, 09 Nov 2002 14:38:00 -0000 From: Daniel Jacobowitz To: Tom Tromey Cc: Gdb List Subject: Re: Two feature suggestions Message-ID: <20021109223958.GA31584@nevyn.them.org> Mail-Followup-To: Tom Tromey , Gdb List References: <87lm42bct4.fsf@fleche.redhat.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <87lm42bct4.fsf@fleche.redhat.com> User-Agent: Mutt/1.5.1i X-SW-Source: 2002-11/txt/msg00101.txt.bz2 On Sat, Nov 09, 2002 at 03:25:43PM -0700, Tom Tromey wrote: > While debugging libgcj today I ran across a couple features I would > find useful. These are applicable to both C++ and Java. > > First, if you have a large inheritance tree, sometimes you don't know > the class which actually defines a given method. For instance, in my > case I want to set a breakpoint on the `validate' method. I'm looking > at an object of type `Window'. Window doesn't implement validate, it > inherits it from its superclass. > > I'd like to be able to type `b java.awt.Window.validate' and have gdb > find the actual implementation for me. Traversing the inheritance > tree is more easily done by gdb than by me. It should already do this. If it doesn't then that's just one of many ways our C++ support isn't coping with Java. > Also, in my case I only want a breakpoint for that method for my > particular window. I'd like to be able to type something like: > > b .validate > > and have it do something like: > > b java.awt.Window.validate > cond this == > > That is, set an object-specific breakpoint on the actual `validate' > method that will be called on the object I'm interested in. > > These are both convenience operations -- I can do them by hand, but > I'd prefer that gdb do the lookups and such for me. I'm not so sure about this one; since you can already say this and it will just breakpoint on the method... -- Daniel Jacobowitz MontaVista Software Debian GNU/Linux Developer