This is the mail archive of the gdb@sources.redhat.com mailing list for the GDB project.

Index Nav:	[Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav:	[Date Prev] [Date Next]	[Thread Prev] [Thread Next]
Other format:	[Raw text]

Re: Binary Compatibility: debug info for compiled Java programs

From: Andrew Cagney <cagney at gnu dot org>
To: Anthony Green <green at redhat dot com>
Cc: Andrew Haley <aph at redhat dot com>, java at gcc dot gnu dot org, gdb at sources dot redhat dot com
Date: Wed, 09 Jun 2004 17:26:12 -0400
Subject: Re: Binary Compatibility: debug info for compiled Java programs
References: <16582.65277.81118.189889@cuddles.cambridge.redhat.com> <1086813967.2819.40.camel@dhcp-172-16-25-229.sfbay.redhat.com>

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.

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.

Andrew

Follow-Ups:
- Re: Binary Compatibility: debug info for compiled Java programs
  - From: Anthony Green
- Re: Binary Compatibility: debug info for compiled Java programs
  - From: Andrew Haley

References:
- Binary Compatibility: debug info for compiled Java programs
  - From: Andrew Haley
- Re: Binary Compatibility: debug info for compiled Java programs
  - From: Anthony Green

Index Nav:	[Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav:	[Date Prev] [Date Next]	[Thread Prev] [Thread Next]