From f4d67a7038ee868061855fc22977b79a12bb2d73 Mon Sep 17 00:00:00 2001 From: Juho Snellman Date: Sun, 22 Mar 2009 19:07:09 +0000 Subject: [PATCH] 1.0.26.11: Fix the error message for ENOMEM on mprotect * Error message was not updated when the variable was renamed * s/size/bytes/, s/parms/backend-parms/ --- src/runtime/linux-os.c | 3 ++- version.lisp-expr | 2 +- 2 files changed, 3 insertions(+), 2 deletions(-) diff --git a/src/runtime/linux-os.c b/src/runtime/linux-os.c index 2e58266..1635132 100644 --- a/src/runtime/linux-os.c +++ b/src/runtime/linux-os.c @@ -363,7 +363,8 @@ os_protect(os_vm_address_t address, os_vm_size_t length, os_vm_prot_t prot) lose("An mprotect call failed with ENOMEM. This probably means that the maximum amount\n" "of separate memory mappings was exceeded. To fix the problem, either increase\n" "the maximum with e.g. 'echo 262144 > /proc/sys/vm/max_map_count' or recompile\n" - "SBCL with a larger value for GENCGC-PAGE-SIZE in 'src/target/parms.lisp'."); + "SBCL with a larger value for GENCGC-PAGE-BYTES in\n" + "'src/compiler/target/backend-parms.lisp'."); } else { perror("mprotect"); } diff --git a/version.lisp-expr b/version.lisp-expr index b5cc8c4..930910c 100644 --- a/version.lisp-expr +++ b/version.lisp-expr @@ -17,4 +17,4 @@ ;;; checkins which aren't released. (And occasionally for internal ;;; versions, especially for internal versions off the main CVS ;;; branch, it gets hairier, e.g. "0.pre7.14.flaky4.13".) -"1.0.26.10" +"1.0.26.11" -- 1.7.10.4