Mirror of the gdb-patches mailing list
 help / color / mirror / Atom feed
From: John Baldwin <jhb@freebsd.org>
To: gdb-patches@sourceware.org
Cc: Joel Brobecker <brobecker@adacore.com>
Subject: Re: New ARI warning Tue Apr 28 01:54:12 UTC 2015
Date: Tue, 28 Apr 2015 16:06:00 -0000	[thread overview]
Message-ID: <4578472.FfTsiG9exU@ralph.baldwin.cx> (raw)
In-Reply-To: <20150428123125.GA4994@adacore.com>

On Tuesday, April 28, 2015 08:31:25 AM Joel Brobecker wrote:
> John,
> 
> On Tue, Apr 28, 2015 at 01:54:13AM +0000, GDB Administrator wrote:
> > 169a170
> > > gdb/fbsd-nat.c:30: regression: wait.h: Do not include wait.h or sys/wait.h, instead include gdb_wait.h
> > gdb/fbsd-nat.c:30:#include <sys/wait.h>
> 
> Looking at the file that triggered this new warning, I'd guess
> this one comes from one of your changes. It might make a little
> less sense in a -nat file to follow that rule, but I don't think
> it'd hurt, and this would avoid increasing the number of ARI hits.
> Would you mind fixing, please?

Not at all, does this look ok?

Use "gdb_wait.h" instead of <sys/wait.h>.

gdb/ChangeLog:
	* fbsd-nat.c: Include "gdb_wait.h" instead of <sys/wait.h>.
---
diff --git a/gdb/fbsd-nat.c b/gdb/fbsd-nat.c
index 066e288..9705d45 100644
--- a/gdb/fbsd-nat.c
+++ b/gdb/fbsd-nat.c
@@ -23,11 +23,11 @@
 #include "regcache.h"
 #include "regset.h"
 #include "gdbthread.h"
+#include "gdb_wait.h"
 #include <sys/types.h>
 #include <sys/procfs.h>
 #include <sys/ptrace.h>
 #include <sys/sysctl.h>
-#include <sys/wait.h>
 #ifdef HAVE_KINFO_GETVMMAP
 #include <sys/user.h>
 #include <libutil.h>
-- 
2.2.1



-- 
John Baldwin


  reply	other threads:[~2015-04-28 15:33 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-04-28 10:03 GDB Administrator
2015-04-28 13:26 ` Joel Brobecker
2015-04-28 16:06   ` John Baldwin [this message]
2015-04-28 16:06     ` Joel Brobecker

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=4578472.FfTsiG9exU@ralph.baldwin.cx \
    --to=jhb@freebsd.org \
    --cc=brobecker@adacore.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