summaryrefslogtreecommitdiff
diff options
context:
space:
mode:
authorIvan Maidanski <ivmai@mail.ru>2021-08-03 09:24:39 +0300
committerIvan Maidanski <ivmai@mail.ru>2021-08-04 11:06:40 +0300
commite62237a1e000a863f011856079cce5bb524eb005 (patch)
tree63bf26e7e39ba7b9b68fc428a70b66653642aa86
parentdcaad02116999a1ebb28707d301dd220f7e96005 (diff)
downloadbdwgc-e62237a1e000a863f011856079cce5bb524eb005.tar.gz
Better document that MPROTECT_VDB is not compatible with REDIRECT_MALLOC
(fix of commit 7f9a90590) * include/private/gcconfig.h [(I386 || X86_64) && LINUX && REDIRECT_MALLOC]: Refine comment (mention fread()).
-rw-r--r--include/private/gcconfig.h4
1 files changed, 2 insertions, 2 deletions
diff --git a/include/private/gcconfig.h b/include/private/gcconfig.h
index c768dbf5..eb2d18a5 100644
--- a/include/private/gcconfig.h
+++ b/include/private/gcconfig.h
@@ -1466,7 +1466,7 @@ EXTERN_C_BEGIN
# else
/* We seem to get random errors in incremental mode, */
/* possibly because Linux threads is itself a malloc client */
- /* and can't deal with the signals. */
+ /* and can't deal with the signals. fread uses malloc too. */
# endif
# define HEAP_START (ptr_t)0x1000
/* This encourages mmap to give us low addresses, */
@@ -2640,7 +2640,7 @@ EXTERN_C_BEGIN
# else
/* We seem to get random errors in incremental mode, */
/* possibly because Linux threads is itself a malloc client */
- /* and can't deal with the signals. */
+ /* and can't deal with the signals. fread uses malloc too. */
# endif
# define COUNT_UNMAPPED_REGIONS
# define DYNAMIC_LOADING