This is the mail archive of the libc-hacker@sourceware.cygnus.com mailing list for the glibc project.

Note that libc-hacker is a closed list. You may look at the archives of this list, but subscription and posting are not open.

Index Nav:	[Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav:	[Date Prev] [Date Next]	[Thread Prev] [Thread Next]

Re: more on the emacs-20.3 segfault

To: schwab@issan.cs.uni-dortmund.de
Subject: Re: more on the emacs-20.3 segfault
From: Wolfram Gloger <wmglo@dent.med.uni-muenchen.de>
Date: 31 May 1999 07:43:55 -0000
CC: Wolfram.Gloger@dent.med.uni-muenchen.de, kimoto@lightlink.com, libc-hacker@sourceware.cygnus.com, pbg1854@garnet.acns.fsu.edu
References: <199905260414.AAA17530@adore.lightlink.com> <19990528101003.2928.qmail@md.dent.med.uni-muenchen.de> <vyzn1ypa2yd.fsf@issan.cs.uni-dortmund.de> <19990528122011.8199.qmail@md.dent.med.uni-muenchen.de> <vyzk8tpadt1.fsf@issan.cs.uni-dortmund.de>

> Unfortunately this has a very nasty side effect: the protection against
> MALLOC_CHECK_ does not work any more.  That means that Emacs will crash if
> MALLOC_CHECK_ is defined in the environment, and there is no way to fix
> that within Emacs (the malloc_initialize_hook runs too late).

OK, I'll take a look at whether this can be fixed in malloc.

Regards,
Wolfram.
-- 
`Surf the sea, not double-u three...'
wmglo@dent.med.uni-muenchen.de

References:
- Re: more on the emacs-20.3 segfault
  - From: Wolfram Gloger <wmglo@dent.med.uni-muenchen.de>
- Re: more on the emacs-20.3 segfault
  - From: Wolfram Gloger <wmglo@dent.med.uni-muenchen.de>
- Re: more on the emacs-20.3 segfault
  - From: Andreas Schwab <schwab@issan.cs.uni-dortmund.de>
- Re: more on the emacs-20.3 segfault
  - From: Andreas Schwab <schwab@issan.cs.uni-dortmund.de>

Index Nav:	[Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav:	[Date Prev] [Date Next]	[Thread Prev] [Thread Next]