Mirror of the gdb-patches mailing list
 help / color / mirror / Atom feed
From: Tom Tromey <tromey@redhat.com>
To: dje@google.com (Doug Evans)
Cc: gdb-patches@sourceware.org, ccoutant@google.com, saugustine@google.com
Subject: Re: [RFA 3/3] Initial Fission support, the actual Fission stuff
Date: Fri, 27 Apr 2012 18:20:00 -0000	[thread overview]
Message-ID: <87397p3usu.fsf@fleche.redhat.com> (raw)
In-Reply-To: <20120418185738.277DB2461AF@ruffy.mtv.corp.google.com> (Doug	Evans's message of "Wed, 18 Apr 2012 11:57:38 -0700 (PDT)")

>>>>> "Doug" == Doug Evans <dje@google.com> writes:

Doug> 	* symfile.h (dwarf2_debug_sections): New members addr, ref.

I think you have to update xcoffread.c as well.

Doug> +  struct bfd *dwo_bfd;

I think it is more normal to use the 'bfd' typedef.
I see a few uses of 'struct bfd' in the tree, but 10x more for the
typedef.

Doug> +      /* We can't set abfd until now because the section may be empty or
Doug> +	 not present, in which case section->asection will be NULL.  */
Doug> +      abfd = section->asection->owner;
Doug> +
Doug>        if (types_htab == NULL)
Doug> -	types_htab = allocate_signatured_type_table (objfile);
Doug> +	{
Doug> +	  if (dwo_file)
Doug> +	    types_htab = allocate_dwo_unit_table (objfile);
Doug> +	  else
Doug> +	    types_htab = allocate_signatured_type_table (objfile);
Doug> +	}
 
Doug>        if (dwarf2_die_debug)
Doug>  	fprintf_unfiltered (gdb_stdlog, "Reading signatured types for %s:\n",
Doug> -			    bfd_get_filename (abfd));
Doug> +			    bfd_get_filename (objfile->obfd));

The code uses abfd, but the debugging print uses objfile->obfd.
If this is intentional, I think it deserves a clarifying comment.

Doug> +	  /* FIXME: Why do ref attributes use DW_ADDR instead of DW_UNSND?  */

Doug> +	  /* FIXME: Why do ref attributes use DW_ADDR instead of DW_UNSND?  */

IIRC you fixed these already.

Doug> +static struct bfd *
Doug> +try_open_dwo_file (const char *file_name)
Doug> +{
Doug> +  bfd *sym_bfd;
[...]

I couldn't find any code to close these BFDs.
I think it may be an oversight in free_dwo_file.

Also, I wonder whether this needs special code for the case where the
underlying object file is modified.

Tom


  parent reply	other threads:[~2012-04-27 18:16 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-04-18 19:12 Doug Evans
2012-04-19  5:07 ` Doug Evans
2012-04-27 18:29   ` Tom Tromey
2012-04-19 10:25 ` Yao Qi
2012-04-19 15:28   ` Doug Evans
2012-04-27 18:38     ` Tom Tromey
2012-04-27 18:20 ` Tom Tromey [this message]
2012-04-28 23:59   ` Doug Evans
2012-04-29  9:05 ` Crash regression for gdb.dwarf2/dw2-inheritance.exp [Re: [RFA 3/3] Initial Fission support, the actual Fission stuff] Jan Kratochvil
2012-04-30  0:06   ` Doug Evans
2012-04-30  2:07     ` Jan Kratochvil
2012-04-30 14:30       ` Doug Evans

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=87397p3usu.fsf@fleche.redhat.com \
    --to=tromey@redhat.com \
    --cc=ccoutant@google.com \
    --cc=dje@google.com \
    --cc=gdb-patches@sourceware.org \
    --cc=saugustine@google.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