From: Yao Qi <yao@codesourcery.com>
To: <gdb-patches@sourceware.org>
Subject: [PATCH 4/6] Use void for empty argument list in trace_me
Date: Mon, 06 Jan 2014 03:56:00 -0000 [thread overview]
Message-ID: <1388980498-10886-5-git-send-email-yao@codesourcery.com> (raw)
In-Reply-To: <1388980498-10886-1-git-send-email-yao@codesourcery.com>
This patch fixes the following error:
../../../git/gdb/gnu-nat.c: In function 'trace_me':
../../../git/gdb/gnu-nat.c:2106:8: error: old-style function definition [-Werror=old-style-definition]
gdb:
2014-01-05 Yao Qi <yao@codesourcery.com>
* gnu-nat.c (trace_me): Use 'void' for empty argument list.
---
gdb/gnu-nat.c | 2 +-
1 files changed, 1 insertions(+), 1 deletions(-)
diff --git a/gdb/gnu-nat.c b/gdb/gnu-nat.c
index ff7df8d..7948677 100644
--- a/gdb/gnu-nat.c
+++ b/gdb/gnu-nat.c
@@ -2103,7 +2103,7 @@ gnu_create_inferior (struct target_ops *ops,
struct inf *inf = cur_inf ();
int pid;
- void trace_me ()
+ void trace_me (void)
{
/* We're in the child; make this process stop as soon as it execs. */
inf_debug (inf, "tracing self");
--
1.7.7.6
next prev parent reply other threads:[~2014-01-06 3:56 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-01-06 3:56 [PATCH 0/6 OBV] Fix compilation errors for hurd Yao Qi
2014-01-06 3:56 ` [PATCH 3/6] Make functions static Yao Qi
2014-01-06 3:56 ` Yao Qi [this message]
2014-01-06 3:56 ` [PATCH 1/6] Fix no previous prototype for '_initialize_gnu_nat' [-Werror=missing-prototypes] Yao Qi
2014-01-06 3:56 ` [PATCH 5/6] Add qualifier 'const' to argument args Yao Qi
2014-01-06 3:56 ` [PATCH 2/6] Remove declaration of inf_tid_to_proc Yao Qi
2014-01-06 3:56 ` [PATCH 6/6] Remove an empty-body 'if' statement Yao Qi
2014-01-06 16:44 ` [PATCH 0/6 OBV] Fix compilation errors for hurd Tom Tromey
2014-01-07 7:14 ` Yao Qi
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=1388980498-10886-5-git-send-email-yao@codesourcery.com \
--to=yao@codesourcery.com \
--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;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).