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: [RFA] typo in cp-valprint.c
Date: Mon, 16 Sep 2002 14:59:00 -0000	[thread overview]
Message-ID: <20020916215850.GA32198@nevyn.them.org> (raw)
In-Reply-To: <ro1ptvdhapc.fsf@jackfruit.Stanford.EDU>

On Mon, Sep 16, 2002 at 02:43:43PM -0700, David Carlton wrote:
> I think there was a typo in one of the recent inclusions of
> check_stub_method_group: I'm getting a compiler warning which seems
> sensible.  This fixes it so this call looks like its other calls.

Er, uh.  Thank you for cleaning up after me, David - please commit
this.

> 
> David Carlton
> carlton@math.stanford.edu
> 
> 2002-09-16  David Carlton  <carlton@math.stanford.edu>
> 
> 	* cp-valprint.c (cp_print_class_method): Correct args to
> 	check_stub_method_group.
> 
> Index: cp-valprint.c
> ===================================================================
> RCS file: /cvs/src/src/gdb/cp-valprint.c,v
> retrieving revision 1.14
> diff -u -p -r1.14 cp-valprint.c
> --- cp-valprint.c	14 Sep 2002 02:09:39 -0000	1.14
> +++ cp-valprint.c	16 Sep 2002 21:40:13 -0000
> @@ -127,7 +127,7 @@ cp_print_class_method (char *valaddr,
>  	  f = TYPE_FN_FIELDLIST1 (domain, i);
>  	  len2 = TYPE_FN_FIELDLIST_LENGTH (domain, i);
>  
> -	  check_stub_method_group (f, j);
> +	  check_stub_method_group (domain, i);
>  	  for (j = 0; j < len2; j++)
>  	    {
>  	      if (STREQ (SYMBOL_NAME (sym), TYPE_FN_FIELD_PHYSNAME (f, j)))
> 

-- 
Daniel Jacobowitz
MontaVista Software                         Debian GNU/Linux Developer


  reply	other threads:[~2002-09-16 21:59 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2002-09-16 14:43 David Carlton
2002-09-16 14:59 ` Daniel Jacobowitz [this message]
2002-09-16 15:04   ` 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=20020916215850.GA32198@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