This is the mail archive of the gdb-testers@sourceware.cygnus.com mailing list for the GDB project. See the GDB home page for more information.
Index Nav: | [Date Index] [Subject Index] [Author Index] [Thread Index] | |
---|---|---|
Message Nav: | [Date Prev] [Date Next] | [Thread Prev] [Thread Next] |
When GDB is configured --with-mmalloc under SunOs 4.1.x sparc/m68k, the resulting GDB issues the following warning upon startup: warning: failed to install memory consistency checks; configuration should define NO_MMCHECK or MMCHECK_FORCE This is caused by inconsistent naming of definitions: gdb/utils.c uses MMCHECK_FORCE, while gdb/configure.in and gdb/acconfig.h use FORCE_MMCHECK. Here is a patch: *** gdb-4.16.85/gdb/acconfig.h.orig Wed Jan 14 05:27:35 1998 --- gdb-4.16.85/gdb/acconfig.h Sat Feb 14 13:21:41 1998 *************** *** 44,47 **** to initialize mmalloc, and we want to force checking to be used anyway. This may cause spurious memory corruption messages if the runtime tries to explicitly deallocate that memory when gdb calls exit. */ ! #undef FORCE_MMCHECK --- 44,47 ---- to initialize mmalloc, and we want to force checking to be used anyway. This may cause spurious memory corruption messages if the runtime tries to explicitly deallocate that memory when gdb calls exit. */ ! #undef MMCHECK_FORCE *** gdb-4.16.85/gdb/configure.in.orig Thu Feb 5 02:42:46 1998 --- gdb-4.16.85/gdb/configure.in Sat Feb 14 13:21:14 1998 *************** *** 279,285 **** if test x$want_mmalloc = xtrue; then AC_DEFINE(USE_MMALLOC) ! AC_DEFINE(FORCE_MMCHECK) MMALLOC_CFLAGS="-I$srcdir/../mmalloc" MMALLOC='../mmalloc/libmmalloc.a' fi --- 279,285 ---- if test x$want_mmalloc = xtrue; then AC_DEFINE(USE_MMALLOC) ! AC_DEFINE(MMCHECK_FORCE) MMALLOC_CFLAGS="-I$srcdir/../mmalloc" MMALLOC='../mmalloc/libmmalloc.a' fi -- Peter Schauer pes@regent.e-technik.tu-muenchen.de