summaryrefslogtreecommitdiffstats
path: root/boehm-gc/README.solaris2
diff options
context:
space:
mode:
Diffstat (limited to 'boehm-gc/README.solaris2')
-rw-r--r--boehm-gc/README.solaris24
1 files changed, 2 insertions, 2 deletions
diff --git a/boehm-gc/README.solaris2 b/boehm-gc/README.solaris2
index 9ef4648d04a..e5935131c77 100644
--- a/boehm-gc/README.solaris2
+++ b/boehm-gc/README.solaris2
@@ -1,7 +1,7 @@
The collector supports both incremental collection and threads under
Solaris 2. The incremental collector normally retrieves page dirty information
through the appropriate /proc calls. But it can also be configured
-(by defining MPROTECT_VDB instead of PROC_VDB in config.h) to use mprotect
+(by defining MPROTECT_VDB instead of PROC_VDB in gcconfig.h) to use mprotect
and signals. This may result in shorter pause times, but it is no longer
safe to issue arbitrary system calls that write to the heap.
@@ -14,7 +14,7 @@ and sbrk() only when you know that malloc() definitely will not be used by
any library routine." This doesn't make a lot of sense to me, since there
seems to be no documentation as to which routines can transitively call malloc.
Nonetheless, under Solaris2, the collector now (since 4.12) allocates
-memory using mmap by default. (It defines USE_MMAP in config.h.)
+memory using mmap by default. (It defines USE_MMAP in gcconfig.h.)
You may want to reverse this decisions if you use -DREDIRECT_MALLOC=...
OpenPOWER on IntegriCloud