Mirror of the gdb-patches mailing list
 help / color / mirror / Atom feed
From: Daniel Jacobowitz <drow@mvista.com>
To: David Carlton <carlton@math.stanford.edu>
Cc: gdb-patches@sources.redhat.com
Subject: Re: [David Carlton <carlton@math.Stanford.EDU>] Re: [RFA] dwarf2read.c: set TYPE_DOMAIN_TYPE correctly for methods
Date: Wed, 28 Aug 2002 15:47:00 -0000	[thread overview]
Message-ID: <20020828224247.GA27335@nevyn.them.org> (raw)
In-Reply-To: <ro17kiahb81.fsf@jackfruit.Stanford.EDU>

On Wed, Aug 28, 2002 at 03:25:50PM -0700, David Carlton wrote:
> Here's a ping for a patch that I'd like to get in before the 5.3
> branch is cut; I'm sending the ping now even though I originally sent
> the patch out just under a week ago because I'll be out of the office
> through next Monday.  (I'm not this pushy normally, honest.)
> 
> The reason why I want to get this into the 5.3 branch is because it
> fixes a seg fault and seg faults make me unduly nervous. :-)

My judgement would be that this fixes an obvious mistake in my previous
patch.


> @@ -2327,7 +2328,15 @@ dwarf2_add_member_fn (struct field_info 
>        struct type *return_type = TYPE_TARGET_TYPE (die->type);
>        int nparams = TYPE_NFIELDS (die->type);
>  
> -      smash_to_method_type (fnp->type, die->type,
> +      /* NOTE: carlton/2002-08-22: Previously, the second argument to
> +	 smash_to_method_type was die->type rather than type, and the
> +	 type argument to dwarf2_add_member_fn didn't exst.  This is
> +	 incorrect: the second argument to smash_to_method_type should
> +	 be the type of the class that this is a method of, whereas
> +	 die->type is the type of the method itself.  So we need to
> +	 pass that type in from read_structure_scope explicitly.  See
> +	 PR gdb/653.  */
> +      smash_to_method_type (fnp->type, type,
>  			    TYPE_TARGET_TYPE (die->type),
>  			    TYPE_FIELDS (die->type),
>  			    TYPE_NFIELDS (die->type),

I'd rather a comment like:
	/* TYPE is the domain of this method, and DIE->TYPE is the type
	   of the method itself (TYPE_CODE_METHOD).  */

There's no point in cluttering up the code with history of this sort
unless you have low confidence in the change's effect on some odd
corner-case.  That's just my personal judgement, though.

If you agree, mind committing it with that or a similar change?

-- 
Daniel Jacobowitz
MontaVista Software                         Debian GNU/Linux Developer


  reply	other threads:[~2002-08-28 22:42 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2002-08-28 15:42 David Carlton
2002-08-28 15:47 ` Daniel Jacobowitz [this message]
2002-08-28 16:43   ` David Carlton
2002-08-28 17:02     ` Andrew Cagney
2002-09-03 10:37   ` David Carlton

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=20020828224247.GA27335@nevyn.them.org \
    --to=drow@mvista.com \
    --cc=carlton@math.stanford.edu \
    --cc=gdb-patches@sources.redhat.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