Re: 22.0.99 emacs dumper (?) problem

[Neal Becker <ndbecker2@gmail.com>]

Chip Coldwell wrote:

> On Fri, 18 May 2007, Neal Becker wrote:
> 
>> Chip Coldwell wrote:
>> 
>> > 
>> > I would like to bring the bug described here:
>> > 
>> > https://bugzilla.redhat.com/bugzilla/show_bug.cgi?id=239344
>> > 
>> > to the attention of this mailing list.  In a nutshell, what happens is
>> > that an emacs binary built using the Fedora 7 build system will
>> > seg-fault immediately when run on a Fedora 7 install.  The stack trace
>> > shows an assert failing in the glibc malloc code (usually it's
>> > setlocale invoking malloc); it appears that something about the way
>> > the dumper preserves the malloc state between the dumping emacs and
>> > the dumped emacs isn't quite working.
>> > 
>> > Another theory that is being examined is that somewhere there is a
>> > pointer to anonymous mmaped memory.  It seems that prepending
>> > 
>> > MALLOC_MMAP_MAX_=0
>> > 
>> > to this line
>> > 
>> > LC_ALL=C $(RUN_TEMACS) -nl -batch -l loadup dump
>> > 
>> > works, although there are some conflicting reports about this, also.
>> > 
>> > Anyway, if we could get some more eyes on this bug, it would probably
>> > help a bunch.
>> > 
>> > Chip
>> > 
>> 
>> This worked for me with emacs-23.0.0.1 until yesterday's update to
>> glibc-2.6-1. (No, I haven't rebuilt emacs today after the glibc-2.6-1
>> update)
> 
> Do you mean that dumping emacs-23.0.0.1 with "MALLOC_MMAP_MAX_=0"
> built a binary that worked with glibc-2.5.90-22 but stopped working
> after the update to glibc-2.6-1?
> 
> emacs-23 is the unicode2 branch, right?  I would assume that the
> malloc hooks, dumper, lisp allocator, etc are common to the two
> branches.
> 
Yes.  What's strange is, I did rebuild again with glibc-2.6-1, and now it's
working again.

Very strange.