Mirror of the gdb-patches mailing list
 help / color / mirror / Atom feed
From: Pedro Alves <pedro@codesourcery.com>
To: gdb-patches@sourceware.org,  Eli Zaretskii <eliz@gnu.org>
Subject: Re: [commit] Fix prototype related breakage in go32-nat.c
Date: Sat, 11 Apr 2009 18:15:00 -0000	[thread overview]
Message-ID: <200904111916.10115.pedro@codesourcery.com> (raw)
In-Reply-To: <834owvoyvb.fsf@gnu.org>

On Saturday 11 April 2009 18:59:20, Eli Zaretskii write:
> Didn't we agree at the time that the prototypes should be corrected as
> well?

You're probably confused...  those functions were changed
much prior to that agreement:

 http://sourceware.org/ml/gdb-patches/2008-08/msg00403.html
 http://sourceware.org/cgi-bin/cvsweb.cgi/src/gdb/go32-nat.c.diff?r1=1.60&r2=1.61&cvsroot=src&f=h

Obviously, it was a simple lapse, one that wouldn't happen if
these functions weren't needlessly forward declared.

(and we agreed to *keep* the prototypes.  Obviously, if they
are to keep, they need to be adjusted, there's no need to agree
on that)

> Committed.
> 
> 
> 2009-04-11  Eli Zaretskii  <eliz@gnu.org>
> 
> 	* go32-nat.c (go32_attach, go32_detach:) Fix prototypes to be

                                              ^ Typo.

> 	consistent with the change from 2009-03-17.

                                        ^^^^^^^^^^
Not that it matter a thing, but, ... wrong date, the change of
the 17th only concerned target_kill.

> 
> Index: gdb/go32-nat.c
> ===================================================================
> RCS file: /cvs/src/src/gdb/go32-nat.c,v
> retrieving revision 1.67
> diff -u -r1.67 go32-nat.c
> --- gdb/go32-nat.c	17 Mar 2009 19:28:08 -0000	1.67
> +++ gdb/go32-nat.c	11 Apr 2009 17:55:06 -0000
> @@ -167,8 +167,8 @@
>  static int prog_has_started = 0;
>  static void go32_open (char *name, int from_tty);
>  static void go32_close (int quitting);
> -static void go32_attach (char *args, int from_tty);
> -static void go32_detach (char *args, int from_tty);
> +static void go32_attach (struct target_ops *ops, char *args, int from_tty);
> +static void go32_detach (struct target_ops *ops, char *args, int from_tty);
>  static void go32_resume (struct target_ops *ops,
>  			 ptid_t ptid, int step,
>  			 enum target_signal siggnal);
> 



-- 
Pedro Alves


  reply	other threads:[~2009-04-11 18:15 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-04-11 18:00 Eli Zaretskii
2009-04-11 18:15 ` Pedro Alves [this message]
2009-04-11 19:27   ` Eli Zaretskii
2009-04-11 20:02     ` Pedro Alves
2009-04-11 21:26       ` Eli Zaretskii
2009-04-13 16:51         ` Tom Tromey
2009-04-13 18:38           ` Eli Zaretskii
2009-04-11 21:41       ` Eli Zaretskii

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=200904111916.10115.pedro@codesourcery.com \
    --to=pedro@codesourcery.com \
    --cc=eliz@gnu.org \
    --cc=gdb-patches@sourceware.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