From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 31416 invoked by alias); 11 Jun 2004 13:04:18 -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 31384 invoked from network); 11 Jun 2004 13:04:12 -0000 Received: from unknown (HELO cuddles.cambridge.redhat.com) (81.96.64.123) by sourceware.org with SMTP; 11 Jun 2004 13:04:12 -0000 Received: from redhat.com (localhost.localdomain [127.0.0.1]) by cuddles.cambridge.redhat.com (8.12.8/8.12.8) with ESMTP id i5BD2hVL027899; Fri, 11 Jun 2004 14:02:53 +0100 Received: (from aph@localhost) by redhat.com (8.12.8/8.12.8/Submit) id i5BD2g8H027895; Fri, 11 Jun 2004 14:02:42 +0100 From: Andrew Haley MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Message-ID: <16585.44402.436252.178470@cuddles.cambridge.redhat.com> Date: Fri, 11 Jun 2004 13:04:00 -0000 To: Andrew Cagney Cc: Anthony Green , java@gcc.gnu.org, gdb@sources.redhat.com Subject: Re: Binary Compatibility: debug info for compiled Java programs In-Reply-To: <40C78074.5020702@gnu.org> References: <16582.65277.81118.189889@cuddles.cambridge.redhat.com> <1086813967.2819.40.camel@dhcp-172-16-25-229.sfbay.redhat.com> <40C78074.5020702@gnu.org> X-SW-Source: 2004-06/txt/msg00114.txt.bz2 Andrew Cagney writes: > > On Wed, 2004-06-09 at 05:13, Andrew Haley wrote: > > > >>> So, I'm still unsure about how to proceed. It looks like Bryce's > >>> suggestion is preferable on efficiency grounds, although it might be > >>> possible to generate DWARF cheaply while laying out classes. > > > > Whatever we do, I'd like to see some solution that attempted to minimize > > communication with the inferior process (for remote debugging > > purposes). > > As an issue, it isn't relevant to this discussion. In either case, whatever we do, we must communicate with the target system to extract structure info. > Andrew asked me about the overhead of extracting data from the inferior. > I sketched out a number of already proposed changes changes, such as > having the inferior agressively supply memory, that would address the > problems you mention. Well, kinda sorta. Anthony is thinking about targets on the end of a wire. Andrew.