Mirror of the gdb-patches mailing list
 help / color / mirror / Atom feed
From: Samuel Thibault via Gdb-patches <gdb-patches@sourceware.org>
To: gdb-patches@sourceware.org,
	Thomas Schwinge <thomas@codesourcery.com>,
	thomas@schwinge.name
Cc: bug-hurd@gnu.org
Subject: [PATCH] hurd: Fix getting VM_MIN/MAX_ADDRESS
Date: Mon, 21 Dec 2020 18:59:10 +0100	[thread overview]
Message-ID: <20201221175910.yv56opyzsdjn6s3f@function> (raw)

gnu-nat.c was getting the inclusion of vm_param.h only by luck. We
need to explicitly include it to be sure to get the definitions of
VM_MIN/MAX_ADDRESS.

gdb/ChangeLog:

        * gnu-nat.c: Include <mach/vm_param.h>.

diff --git a/gdb/gnu-nat.c b/gdb/gnu-nat.c
index 1693ce0c43..6f290be0d5 100644
--- a/gdb/gnu-nat.c
+++ b/gdb/gnu-nat.c
@@ -32,6 +32,7 @@ extern "C"
 #include <mach/message.h>
 #include <mach/notify.h>
 #include <mach/vm_attributes.h>
+#include <mach/vm_param.h>
 
 #include <hurd.h>
 #include <hurd/interrupt.h>

             reply	other threads:[~2020-12-21 17:59 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-12-21 17:59 Samuel Thibault via Gdb-patches [this message]
2020-12-21 19:40 ` Simon Marchi via Gdb-patches
2020-12-22 22:39   ` Samuel Thibault via Gdb-patches
2020-12-22 23:24     ` [PATCH] hurd: Fix getting VM_MIN/MAX_ADDRESS OFF TOPIC PRAISE Joshua Branson via Gdb-patches
2020-12-23  0:09       ` Simon Marchi via Gdb-patches
2020-12-23  0:39         ` Samuel Thibault via Gdb-patches
2020-12-23  3:02           ` Simon Marchi via Gdb-patches
2020-12-23 17:01             ` Samuel Thibault via Gdb-patches
2020-12-23 17:07               ` Simon Marchi via Gdb-patches
2020-12-23 17:22                 ` Samuel Thibault via Gdb-patches

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=20201221175910.yv56opyzsdjn6s3f@function \
    --to=gdb-patches@sourceware.org \
    --cc=bug-hurd@gnu.org \
    --cc=samuel.thibault@gnu.org \
    --cc=thomas@codesourcery.com \
    --cc=thomas@schwinge.name \
    /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