From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 17490 invoked by alias); 9 Jun 2004 22:11:21 -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 17248 invoked from network); 9 Jun 2004 22:11:11 -0000 Received: from unknown (HELO mx1.redhat.com) (66.187.233.31) by sourceware.org with SMTP; 9 Jun 2004 22:11:11 -0000 Received: from int-mx2.corp.redhat.com (int-mx2.corp.redhat.com [172.16.27.26]) by mx1.redhat.com (8.12.10/8.12.10) with ESMTP id i59MB7i5004054 for ; Wed, 9 Jun 2004 18:11:07 -0400 Received: from potter.sfbay.redhat.com (potter.sfbay.redhat.com [172.16.27.15]) by int-mx2.corp.redhat.com (8.11.6/8.11.6) with ESMTP id i59MB6w25556; Wed, 9 Jun 2004 18:11:06 -0400 Received: from [172.16.25.229] (dhcp-172-16-25-229.sfbay.redhat.com [172.16.25.229]) by potter.sfbay.redhat.com (8.11.6/8.11.6) with ESMTP id i59MB5P13977; Wed, 9 Jun 2004 15:11:05 -0700 Subject: Re: Binary Compatibility: debug info for compiled Java programs From: Anthony Green To: Andrew Cagney Cc: Andrew Haley , java@gcc.gnu.org, gdb@sources.redhat.com 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> Content-Type: text/plain Organization: Red Hat, Inc. Message-Id: <1086819049.2819.54.camel@dhcp-172-16-25-229.sfbay.redhat.com> Mime-Version: 1.0 Date: Wed, 09 Jun 2004 22:11:00 -0000 Content-Transfer-Encoding: 7bit X-SW-Source: 2004-06/txt/msg00083.txt.bz2 On Wed, 2004-06-09 at 14:26, Andrew Cagney wrote: > > 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. > > 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. I'm afraid I don't understand what you mean. AG -- Anthony Green Red Hat, Inc.