On Sun, 7 Dec 2008 11:51:51 -0500 Adrian Robert <adrian.b.rob...@gmail.com> wrote:
AR> Here's a fix for this that causes a call to abort() when sig is not 0 AR> or SIGTERM. (At this point emacs.c itself has already done what AR> autosaving etc. it can so should do no harm.) Does this help and AR> generate a stack trace? If so I'll check it in. Hi Adrian, I've been using the Emacs.app code from the Emacs CVS and haven't seen a stack trace or a crash dialog yet. The good news is that I haven't seen a crash yet, either, from around that time (before, Emacs.app crashed very frequently). I wanted to report that, in case you were wondering, but also for the benefit of this list. I know there are other outstanding bug reports and issues, but overall stability was my top gripe and I appreciate the work you've put into Emacs.app to make it better. Tanks Ted ------------------------------------------------------------------------------ This SF.net email is sponsored by: SourcForge Community SourceForge wants to tell your story. http://p.sf.net/sfu/sf-spreadtheword _______________________________________________ Emacs-app-dev- mailing list Emacs-app-dev-@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/emacs-app-dev-
