Mirror of the gdb-patches mailing list
 help / color / mirror / Atom feed
From: Daniel Jacobowitz <drow@false.org>
To: r6144 <r6k@sohu.com>
Cc: gdb-patches@sources.redhat.com
Subject: Re: [RFA/dwarf] Partial DIE support for specifications
Date: Sat, 03 Apr 2004 22:17:00 -0000	[thread overview]
Message-ID: <20040403221725.GA9992@nevyn.them.org> (raw)
In-Reply-To: <16494.59235.964535.885069@localhost.localdomain>

On Sun, Apr 04, 2004 at 12:33:39AM +0800, r6144 wrote:
Content-Description: message body text
> I'm relatively new to gdb hacking.  Does it mean that
> inter-compilation-unit references will work and
> -feliminate-dwarf2-dups will work?  That would be great :)

No, but try the branch I posted information about to gdb@ in the end of
February.  I think I cc'd you.

-- 
Daniel Jacobowitz
MontaVista Software                         Debian GNU/Linux Developer


  reply	other threads:[~2004-04-03 22:17 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2004-04-03 16:33 r6144
2004-04-03 22:17 ` Daniel Jacobowitz [this message]
  -- strict thread matches above, loose matches on Subject: below --
2004-04-02 20:47 Daniel Jacobowitz
2004-04-12 21:14 ` Daniel Jacobowitz
2004-04-15  7:31 ` Jim Blandy
2004-04-16 15:18   ` Daniel Jacobowitz
2004-04-16 21:30     ` Jim Blandy

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=20040403221725.GA9992@nevyn.them.org \
    --to=drow@false.org \
    --cc=gdb-patches@sources.redhat.com \
    --cc=r6k@sohu.com \
    /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