From: Bryce McKinlay Date: Wed, 3 Nov 1999 03:04:52 +0000 (+0000) Subject: gcconfig.h: Don't define MPROTECT_VDB on Linux/i386. X-Git-Url: http://review.tizen.org/git/?a=commitdiff_plain;h=765de7ea9802b252ed8d8bf5092fcd0e8bdbab6f;p=platform%2Fupstream%2Fgcc.git gcconfig.h: Don't define MPROTECT_VDB on Linux/i386. 1999-11-02 Bryce McKinlay * gcconfig.h: Don't define MPROTECT_VDB on Linux/i386. From-SVN: r30364 --- diff --git a/boehm-gc/ChangeLog b/boehm-gc/ChangeLog index 80404ee..b9505ae 100644 --- a/boehm-gc/ChangeLog +++ b/boehm-gc/ChangeLog @@ -1,3 +1,7 @@ +1999-11-02 Bryce McKinlay + + * gcconfig.h: Don't define MPROTECT_VDB on Linux/i386. + 1999-11-02 Tom Tromey * quick_threads.c: Include gcconfig.h, not boehm-config.h. diff --git a/boehm-gc/gcconfig.h b/boehm-gc/gcconfig.h index 4721909..384a465 100644 --- a/boehm-gc/gcconfig.h +++ b/boehm-gc/gcconfig.h @@ -713,7 +713,9 @@ /* with 2GB physical memory will usually move the user */ /* address space limit, and hence initial SP to 0x80000000. */ # if !defined(LINUX_THREADS) || !defined(REDIRECT_MALLOC) -# define MPROTECT_VDB + /* libgcj: Linux threads don't interact well with the read() wrapper. + Not defining MPROTECT_VDB fixes this. */ +/* # define MPROTECT_VDB */ # else /* We seem to get random errors in incremental mode, */ /* possibly because Linux threads is itself a malloc client */