Mirror of the gdb mailing list
 help / color / mirror / Atom feed
From: Andrew Haley <aph@redhat.com>
To: Andrew Cagney <cagney@gnu.org>
Cc: Anthony Green <green@redhat.com>,
	java@gcc.gnu.org, gdb@sources.redhat.com
Subject: Re: Binary Compatibility: debug info for compiled Java programs
Date: Fri, 11 Jun 2004 13:04:00 -0000	[thread overview]
Message-ID: <16585.44402.436252.178470@cuddles.cambridge.redhat.com> (raw)
In-Reply-To: <40C78074.5020702@gnu.org>

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.


  parent reply	other threads:[~2004-06-11 13:04 UTC|newest]

Thread overview: 23+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2004-06-09 12:15 Andrew Haley
2004-06-09 13:09 ` Daniel Jacobowitz
2004-06-09 13:19   ` Andrew Haley
2004-06-09 13:29     ` Daniel Jacobowitz
2004-06-09 13:39       ` Andrew Haley
2004-06-09 22:17         ` Daniel Jacobowitz
2004-06-09 22:37           ` Tom Tromey
2004-06-10 16:37             ` Daniel Jacobowitz
2004-06-10 16:42               ` Tom Tromey
2004-06-10 16:47                 ` Ian Lance Taylor
2004-06-10 16:58                   ` Andrew Haley
2004-06-10 17:12                     ` Ian Lance Taylor
2004-06-10 17:25                       ` Andrew Haley
2004-06-10 16:44               ` Andrew Haley
2004-06-10 16:54                 ` Daniel Jacobowitz
2004-06-09 14:13 ` Per Bothner
2004-06-09 14:20   ` Andrew Haley
2004-06-09 20:46 ` Anthony Green
2004-06-09 21:26   ` Andrew Cagney
2004-06-09 22:11     ` Anthony Green
2004-06-11 13:04     ` Andrew Haley [this message]
2004-06-11 15:11       ` Andrew Cagney
2004-06-11 15:17         ` Andrew Haley

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=16585.44402.436252.178470@cuddles.cambridge.redhat.com \
    --to=aph@redhat.com \
    --cc=cagney@gnu.org \
    --cc=gdb@sources.redhat.com \
    --cc=green@redhat.com \
    --cc=java@gcc.gnu.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox