VM_MAXUSER_ADDRESS can be undefined when compiling module/coredump;

it varies between machines for evbppc (and possibly evbppc64).
This commit is contained in:
rin 2019-02-17 13:46:03 +00:00
parent 919fe1ff1f
commit 514df72f81

View File

@ -1,4 +1,4 @@
/* $NetBSD: uvm_coredump.c,v 1.6 2014/01/07 07:59:03 dsl Exp $ */
/* $NetBSD: uvm_coredump.c,v 1.7 2019/02/17 13:46:03 rin Exp $ */
/*
* Copyright (c) 1997 Charles D. Cranor and Washington University.
@ -62,7 +62,7 @@
*/
#include <sys/cdefs.h>
__KERNEL_RCSID(0, "$NetBSD: uvm_coredump.c,v 1.6 2014/01/07 07:59:03 dsl Exp $");
__KERNEL_RCSID(0, "$NetBSD: uvm_coredump.c,v 1.7 2019/02/17 13:46:03 rin Exp $");
/*
* uvm_coredump.c: glue functions for coredump
@ -130,8 +130,10 @@ uvm_coredump_walkmap(struct proc *p, int (*func)(struct uvm_coredump_state *),
*/
KASSERT(!UVM_ET_ISSUBMAP(entry));
#ifdef VM_MAXUSER_ADDRESS
KASSERT(state.start < VM_MAXUSER_ADDRESS);
KASSERT(state.end <= VM_MAXUSER_ADDRESS);
#endif
if (entry->object.uvm_obj == NULL &&
entry->aref.ar_amap == NULL) {
state.realend = state.start;