Mirror of the gdb-patches mailing list
 help / color / mirror / Atom feed
From: Yao Qi <qiyaoltc@gmail.com>
To: gdb-patches@sourceware.org
Subject: [PATCH OBV 07/10] Include signal.h in nat/amd64-linux-siginfo.h
Date: Fri, 06 Jan 2017 14:19:00 -0000	[thread overview]
Message-ID: <1483712340-9157-7-git-send-email-yao.qi@linaro.org> (raw)
In-Reply-To: <1483712340-9157-1-git-send-email-yao.qi@linaro.org>

$ make check-headers CHECK_HEADERS="nat/amd64-linux-siginfo.h"
....
../../binutils-gdb/gdb/nat/amd64-linux-siginfo.h:52:39: error: 'siginfo_t' was not declared in this scope
 int amd64_linux_siginfo_fixup_common (siginfo_t *native, gdb_byte *inf,
                                       ^
gdb:

2017-01-06  Yao Qi  <yao.qi@linaro.org>

	* nat/amd64-linux-siginfo.h: Include signal.h.
---
 gdb/nat/amd64-linux-siginfo.h | 2 ++
 1 file changed, 2 insertions(+)

diff --git a/gdb/nat/amd64-linux-siginfo.h b/gdb/nat/amd64-linux-siginfo.h
index 452a9f1..ccc71c8 100644
--- a/gdb/nat/amd64-linux-siginfo.h
+++ b/gdb/nat/amd64-linux-siginfo.h
@@ -20,6 +20,8 @@
 #ifndef AMD64_LINUX_SIGINFO_H
 #define AMD64_LINUX_SIGINFO_H 1
 
+#include <signal.h>  /* For siginfo_t.  */
+
 /* When GDB is built as a 64-bit application on Linux, the
    PTRACE_GETSIGINFO data is always presented in 64-bit layout.  Since
    debugging a 32-bit inferior with a 64-bit GDB should look the same
-- 
1.9.1


  parent reply	other threads:[~2017-01-06 14:19 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-01-06 14:19 [PATCH 01/10] 'make check-headers' for c++ header Yao Qi
2017-01-06 14:19 ` [PATCH OBV 02/10] Include ax.h in ax-gdb.h Yao Qi
2017-01-06 14:19 ` [PATCH OBV 05/10] Include mi-cmds.h in mi-parse.h Yao Qi
2017-01-06 14:19 ` [PATCH OBV 09/10] Include serial.h in ser-base.h Yao Qi
2017-01-06 14:19 ` Yao Qi [this message]
2017-01-06 14:19 ` [PATCH OBV 10/10] Include gdb_proc_service.h in x86-linux-nat.h Yao Qi
2017-01-06 14:19 ` [PATCH OBV 06/10] Include break-common.h in nat/aarch64-linux-hw-point.h Yao Qi
2017-01-06 14:19 ` [PATCH OBV 08/10] Include ppc-tdep.h in ppc-linux-tdep.h Yao Qi
2017-01-06 14:19 ` [PATCH OBV 03/10] Include doublest.h and expression.h in dfp.h Yao Qi
2017-01-06 14:19 ` [PATCH OBV 04/10] Include target.h in inf-loop.h Yao Qi
2017-01-13 14:41 ` [PATCH 01/10] 'make check-headers' for c++ header 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=1483712340-9157-7-git-send-email-yao.qi@linaro.org \
    --to=qiyaoltc@gmail.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