public inbox for insight@sourceware.org
 help / color / mirror / Atom feed
From: Keith Seitz <keiths@redhat.com>
To: insight <insight@sourceware.org>
Subject: [PATCH] Add missing prototypes
Date: Sat, 10 Mar 2012 21:53:00 -0000	[thread overview]
Message-ID: <4F5BCD29.9010500@redhat.com> (raw)

[-- Attachment #1: Type: text/plain, Size: 279 bytes --]

Hi,

Gdb recently added -Wmissing-prototypes. This patch fixes the one build 
regression caused by this.

Keith

ChangeLog
2012-03-10  Keith Seitz  <keiths@redhat.com>

	* generic/gdbtk-interp.c (_initialize_gdbtk_interp): Add
	missing prototype to appease -Wmissing-prototypes.

[-- Attachment #2: missing-proto.patch --]
[-- Type: text/x-patch, Size: 826 bytes --]

Index: generic/gdbtk-interp.c
===================================================================
RCS file: /cvs/src/src/gdb/gdbtk/generic/gdbtk-interp.c,v
retrieving revision 1.11
diff -u -p -r1.11 gdbtk-interp.c
--- generic/gdbtk-interp.c	2 Nov 2011 19:44:37 -0000	1.11
+++ generic/gdbtk-interp.c	10 Mar 2012 21:51:32 -0000
@@ -1,7 +1,7 @@
 /* Insight Definitions for GDB, the GNU debugger.
    Written by Keith Seitz <kseitz@sources.redhat.com>
 
-   Copyright (C) 2003, 2004, 2008, 2011 Free Software Foundation, Inc.
+   Copyright (C) 2003, 2004, 2008, 2011, 2012 Free Software Foundation, Inc.
 
    This file is part of Insight.
 
@@ -42,6 +42,7 @@
 
 static void gdbtk_command_loop (void);
 static void hack_disable_interpreter_exec (char *, int);
+void _initialize_gdbtk_interp (void);
 
 struct gdbtk_interp_data
 {

                 reply	other threads:[~2012-03-10 21:53 UTC|newest]

Thread overview: [no followups] expand[flat|nested]  mbox.gz  Atom feed

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=4F5BCD29.9010500@redhat.com \
    --to=keiths@redhat.com \
    --cc=insight@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;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).