From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 3632 invoked by alias); 14 May 2007 20:02:05 -0000 Received: (qmail 3617 invoked by uid 22791); 14 May 2007 20:02:03 -0000 X-Spam-Check-By: sourceware.org Received: from return.false.org (HELO return.false.org) (66.207.162.98) by sourceware.org (qpsmtpd/0.31) with ESMTP; Mon, 14 May 2007 20:02:01 +0000 Received: from return.false.org (localhost [127.0.0.1]) by return.false.org (Postfix) with ESMTP id A320F4B267; Mon, 14 May 2007 15:01:57 -0500 (CDT) Received: from caradoc.them.org (dsl093-172-095.pit1.dsl.speakeasy.net [66.93.172.95]) by return.false.org (Postfix) with ESMTP id 7D3874B262; Mon, 14 May 2007 15:01:57 -0500 (CDT) Received: from drow by caradoc.them.org with local (Exim 4.67) (envelope-from ) id 1Hngk0-0003ul-QD; Mon, 14 May 2007 16:01:56 -0400 Date: Mon, 14 May 2007 20:02:00 -0000 From: Daniel Jacobowitz To: Tom Tromey Cc: gdb-patches@sourceware.org Subject: Re: [commit] Minor java fixups Message-ID: <20070514200156.GA15006@caradoc.them.org> Mail-Followup-To: Tom Tromey , gdb-patches@sourceware.org References: <20070514164933.GA3350@caradoc.them.org> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: User-Agent: Mutt/1.5.15 (2007-04-09) 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: 2007-05/txt/msg00254.txt.bz2 On Mon, May 14, 2007 at 01:35:26PM -0600, Tom Tromey wrote: > >>>>> "Daniel" == Daniel Jacobowitz writes: > > Daniel> GDB's Java support is getting very rusty. I think it's been several > Daniel> releases since it was able to print objects, and it's even worse now > Daniel> that we only get a declaration for java.lang.Object in the debug info. > > FWIW most gcj developers now use the runtime debugging support > functions that Andrew wrote -- _Jv_Debug and friends. These generally > seem more reliable than gdb's "print" ever was. (Not that this is > necessarily gdb's fault. It is just that few people have ever > ventured into this area to find and fix bugs.) It's the "fault" of the nebulous non-developer who is working on GDB's Java support :-) I'd be delighted if someone stepped up and was interested. -- Daniel Jacobowitz CodeSourcery