Re: [Mac-emacs-users] 'Fatal error (6).Abort'

[Steven T. <ste...@ma...>]

I hit the exact same problem.  After the security update I had to 
recompile from scratch or else I got Fatal Error (10).  I assumed -nw 
was the problem (probably falsely), but hopefully the patch I posted to 
the mac-emacs-devel list will fix that.

WRT, the security update, I think the problem might be in the whole 
unexec process.  That is where a preliminary emacs (just compiled C 
code) reads in a bunch of lisp and then spits itself out as an 
executable (so I doesn't take too long to load up).  I have found that 
when I try to run update_prebinding, it complains that it cannot update 
Emacs.  Since update_prebinding is what the installer does when it says 
"Optimizing" I assumed that unexec might not be spitting out the right 
prebinding.  However, older versions of emacs I had lying around seemed 
to still work after the update so I could be barking up the wrong tree.

Maybe the author of the unexmacosx.c code has an idea?

-Steven

On Wednesday, August 7, 2002, at 01:00  PM, Amos wrote:

>>>>>> On Wed, 7 Aug 2002 13:42:51 -0400,
>>>>>> Michael P Wilson <mpw...@ea...> (mpw) writes:
>
> mpw> I pulled the cvs current a couple days ago, configured, built &
> mpw> installed the code, but execution give me the very descriptive 
> error
> mpw> "Fatal error (6).Abort".
>
> Did you install the latest Mac OS X security update since the CVS
> build?  I noticed something quite similar after installing that OS
> X update.  My guess at the time was that Emacs didn't care for the
> change in libraries.  So I figured it was time to suck down another
> CVS update and redo the build.  Things have been peachy since....
>
> --
> Amos
>
>
>
> -------------------------------------------------------
> This sf.net email is sponsored by:ThinkGeek
> Welcome to geek heaven.
> http://thinkgeek.com/sf
> _______________________________________________
> Mac-emacs-users mailing list
> Mac...@li...
> https://lists.sourceforge.net/lists/listinfo/mac-emacs-users