From: Marcin Cieslak <saper@saper.info>
To: gdb-patches@sourceware.org
Subject: [PATCH] procfs.c: Include "filestuff.h"
Date: Tue, 18 Aug 2015 18:08:00 -0000 [thread overview]
Message-ID: <alpine.BSF.2.11.1508181807170.7491@z.fncre.vasb> (raw)
Fixes implicit function declaration
error in procfs.c:4927 about undeclared
make_cleanup_close().
gdb/ChangeLog:
PR gdb/18843
* procfs.c: Include "filestuff.h"
---
gdb/ChangeLog | 5 +++++
gdb/procfs.c | 1 +
2 files changed, 6 insertions(+)
diff --git a/gdb/ChangeLog b/gdb/ChangeLog
index 4af881e..edb4d88 100644
--- a/gdb/ChangeLog
+++ b/gdb/ChangeLog
@@ -1,3 +1,8 @@
+2015-08-18 Marcin CieÂślak <saper@saper.info>
+
+ PR gdb/18843
+ * procfs.c: Include "filestuff.h"
+
2015-08-18 Sandra Loosemore <sandra@codesourcery.com>
* remote.c (strprefix): New.
diff --git a/gdb/procfs.c b/gdb/procfs.c
index 42f1403..3d4f7be 100644
--- a/gdb/procfs.c
+++ b/gdb/procfs.c
@@ -30,6 +30,7 @@
#include "gdbthread.h"
#include "regcache.h"
#include "inf-child.h"
+#include "filestuff.h"
#if defined (NEW_PROC_API)
#define _STRUCTURED_PROC 1 /* Should be done by configure script. */
--
2.5.0
next reply other threads:[~2015-08-18 18:08 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-08-18 18:08 Marcin Cieslak [this message]
2015-08-19 7:54 ` Yao Qi
2015-08-19 16:51 ` Marcin Cieslak
2015-08-19 16:52 ` Marcin Cieslak
2015-08-21 8:21 ` 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=alpine.BSF.2.11.1508181807170.7491@z.fncre.vasb \
--to=saper@saper.info \
--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