Olivier Galibert <galibert(a)pobox.com&gt; writes: Even with both my changes to get it to the actual dump case it crashes in the dump Dumping under the name xemacs Fatal error: assertion failed, file alloc.c, line 4206, !pdump_get_entry(obj) Abort - core dumped This is the backtrace #1 0xef03a5e8 in abort () #2 0x6b1c4 in pdump_register_sub () #3 0x6be1c in pdump_register_object () #4 0x6b464 in pdump_register_sub () #5 0x6ba60 in pdump_register_sub () #6 0x6ba60 in pdump_register_sub () #7 0x6d83c in pdump () #8 0xe4cf4 in Fdump_emacs () Note that this is Solaris CC with the default CC flags, i.e. inlining and not debug symbols. This explains why pdump_add_entry does not appear in the backtrace although the insert is there. I have no time left. In an attempt to be usefull I changed the code around that assert to read static void pdump_backtrace(void); static void pdump_add_entry(pdump_entry_list *list, const void *obj, size_t size, int is_lrecord) { pdump_entry_list_elmt *e; int align; if (pdump_get_entry(obj)) { pdump_backtrace(); assert (!pdump_get_entry(obj)); } This then gives Dumping under the name xemacs pdump backtrace : - ind. (0, 0) - ind. (1, 4) - ind. (0, 4) - subr (0, 12) Fatal error: assertion failed, file alloc.c, line 4211, !pdump_get_entry(obj) Abort I hope this output is meaningfull to you Jan uname -a: SunOS bolzano 5.5.1 Generic_103640-08 sun4u sparc SUNW,Ultra-1 /configure '--prefix=/scratch/vroonhof/xe205' '--with-site-lisp' '-with-gcc=no' '--with-mule=yes' '--with-workshop=no' '--site-libraries=/usr/local/lib:/u/scratch/jvsoft/lib:/u/scratch/jvsoft/canna/lib' '--site-runtime-libraries=/usr/local/lib:/u/scratch/jvsoft/lib:/u/scratch/jvsoft/canna/lib' '--site-includes=/usr/local/app/libpng/1.0.3/include/:/usr/local/include:/u/scratch/jvsoft/include:/u/scratch/jvsoft/canna/include' XEmacs 21.1.6 "Big Bend" configured for `sparc-sun-solaris2.5.1'. Where should the build process find the source code? /scratch/vroonhof/cvs/xemacs-20 What installation prefix should install use? /scratch/vroonhof/xe205 What operating system and machine description files should XEmacs use? `s/sol2.h' and `m/sparc.h' What compiler should XEmacs be built with? cc -v -xO4 Should XEmacs use the GNU version of malloc? yes Should XEmacs use the relocating allocator for buffers? yes What window system should XEmacs use? x11 Where do we find X Windows header files? /usr/dt/include /usr/local/X11/include Where do we find X Windows libraries? /usr/dt/lib /usr/local/X11/lib Additional header files: /usr/local/app/libpng/1.0.3/include/ /usr/local/include /u/scratch/jvsoft/include /u/scratch/jvsoft/canna/include Additional libraries: /usr/local/lib /u/scratch/jvsoft/lib /u/scratch/jvsoft/canna/lib Runtime library search path: /usr/local/lib:/u/scratch/jvsoft/lib:/u/scratch/jvsoft/canna/lib Compiling in support for XAUTH. Compiling in support for XPM images. Compiling in support for PNG image handling. Compiling in support for (builtin) GIF image handling. Compiling in support for JPEG image handling. Compiling in support for X-Face message headers. Compiling in support for Berkeley DB. Compiling in support for DBM. Compiling in Mule (multi-lingual) support. Compiling in XIM (X11R5+ I18N input method) support. Using Motif to provide XIM support. Compiling in support for Canna on Mule. Compiling in support for ToolTalk. Compiling in support for proper session-management. Using Lucid menubars. Using Lucid scrollbars. Using Motif dialog boxes. Compiling in DLL support. movemail will use "dot-locking" for locking mail spool files.