From: Kamil Rytarowski <n54@gmx.com>
To: gdb-patches@sourceware.org
Subject: [PATCH] Include missing header to get missing declarations
Date: Mon, 16 Mar 2020 18:29:22 +0100 [thread overview]
Message-ID: <20200316172922.3548-1-n54@gmx.com> (raw)
CXX amd64-bsd-nat.o
amd64-bsd-nat.c:42:1: error: no previous declaration void amd64bsd_fetch_inferior_registers(regcache*, [-Werror=missing-declarations]
amd64bsd_fetch_inferior_registers (struct regcache *regcache, int regnum)
^~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
amd64-bsd-nat.c:118:1: error: no previous declaration void amd64bsd_store_inferior_registers(regcache*, [-Werror=missing-declarations]
amd64bsd_store_inferior_registers (struct regcache *regcache, int regnum)
^~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
Detected on NetBSD/amd64 9.99.49.
gdb/ChangeLog:
* amd64-bsd-nat.c: Include amd64-bsd-nat.h".
---
gdb/ChangeLog | 4 ++++
gdb/amd64-bsd-nat.c | 1 +
2 files changed, 5 insertions(+)
diff --git a/gdb/ChangeLog b/gdb/ChangeLog
index a0d97584189..d52e3242256 100644
--- a/gdb/ChangeLog
+++ b/gdb/ChangeLog
@@ -1,3 +1,7 @@
+2020-03-17 Kamil Rytarowski <n54@gmx.com>
+
+ * amd64-bsd-nat.c: Include amd64-bsd-nat.h".
+
2020-03-14 Tom Tromey <tom@tromey.com>
* c-typeprint.c (cp_type_print_method_args): Print "__restrict__"
diff --git a/gdb/amd64-bsd-nat.c b/gdb/amd64-bsd-nat.c
index d2be4bb2399..9a3c9c22c05 100644
--- a/gdb/amd64-bsd-nat.c
+++ b/gdb/amd64-bsd-nat.c
@@ -33,6 +33,7 @@
#include "amd64-nat.h"
#include "x86-bsd-nat.h"
#include "inf-ptrace.h"
+#include "amd64-bsd-nat.h"
\f
/* Fetch register REGNUM from the inferior. If REGNUM is -1, do this
--
2.25.0
next reply other threads:[~2020-03-16 17:30 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-03-16 17:29 Kamil Rytarowski [this message]
2020-03-16 17:36 ` Simon Marchi
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=20200316172922.3548-1-n54@gmx.com \
--to=n54@gmx.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