Mirror of the gdb mailing list
 help / color / mirror / Atom feed
From: Daniel Jacobowitz <drow@mvista.com>
To: "H. J. Lu" <hjl@lucon.org>
Cc: GDB <gdb@sources.redhat.com>
Subject: Re: DW_FORM_ref_addr dosn't work
Date: Wed, 30 Jul 2003 21:45:00 -0000	[thread overview]
Message-ID: <20030730214503.GA15350@nevyn.them.org> (raw)
In-Reply-To: <20030730214252.GA26082@lucon.org>

On Wed, Jul 30, 2003 at 02:42:52PM -0700, H. J. Lu wrote:
> DW_FORM_ref_addr can reference an entry in a different compilation
> unit, even from a different shared object. But die_ref_table only
> contains DIEs in one single compilation unit. Why do we do that? What
> is the best way to fix it?
> 
> BTW, I am enclosing my quick dirty hack for reference.

Please read any of the thirty-some discussions of this in the list
archives.

I'm working on it in my spare time, of which I have not had enough to
make much progress.  The DWARF reader needs to be essentially
rewritten.

> 
> 
> H.J.
> ----
> --- dwarf2read.c.ref	2003-07-30 09:43:51.000000000 -0700
> +++ dwarf2read.c	2003-07-30 14:41:24.000000000 -0700
> @@ -1195,6 +1195,7 @@ dwarf2_build_psymtabs_hard (struct objfi
>    struct partial_symtab *pst;
>    struct cleanup *back_to;
>    CORE_ADDR lowpc, highpc;
> +  struct die_info *dies;
>  
>    info_ptr = dwarf_info_buffer;
>    abbrev_ptr = dwarf_abbrev_buffer;
> @@ -1280,6 +1281,8 @@ dwarf2_build_psymtabs_hard (struct objfi
>        dwarf2_read_abbrevs (abfd, &cu_header);
>        make_cleanup (dwarf2_empty_abbrev_table, cu_header.dwarf2_abbrevs);
>  
> +      dies = read_comp_unit (info_ptr, abfd, &cu_header);
> +
>        /* Read the compilation unit die */
>        info_ptr = read_partial_die (&comp_unit_die, abfd, info_ptr,
>  				   &cu_header);
> @@ -3654,9 +3657,11 @@ read_comp_unit (char *info_ptr, bfd *abf
>    char *cur_ptr;
>    int nesting_level;
>  
> +#if 0
>    /* Reset die reference table; we are
>       building new ones now.  */
>    dwarf2_empty_hash_tables ();
> +#endif
>  
>    cur_ptr = info_ptr;
>    nesting_level = 0;
> 

-- 
Daniel Jacobowitz
MontaVista Software                         Debian GNU/Linux Developer


  reply	other threads:[~2003-07-30 21:45 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2003-07-30 21:42 H. J. Lu
2003-07-30 21:45 ` Daniel Jacobowitz [this message]
2003-07-30 21:52   ` H. J. Lu
2003-07-30 21:55     ` Daniel Jacobowitz
2003-07-30 22:01       ` H. J. Lu
2003-07-31  5:16       ` H. J. Lu
2003-07-31 16:16         ` A hack for DW_FORM_ref_addr H. J. Lu
2003-07-31 18:22           ` Daniel Jacobowitz
2003-07-31 18:29             ` H. J. Lu
2003-07-31 22:33               ` Daniel Berlin
2003-07-31 21:21             ` H. J. Lu

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=20030730214503.GA15350@nevyn.them.org \
    --to=drow@mvista.com \
    --cc=gdb@sources.redhat.com \
    --cc=hjl@lucon.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