On Jan 27, 2009, at 10:22 PM, Ted Zlatanov wrote: > On Sun, 7 Dec 2008 11:51:51 -0500 Adrian Robert > <[email protected]> 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.
Good to hear. Hopefully with the feature freeze and now the upcoming move to pretest things will continue to improve. There may still be a couple of bumps in the road (I just checked in another Ctrl-g related fix today), and there may be some menu implementation changes. But aside from that I hope to avoid introducing new any bugs from now on! ;-) ------------------------------------------------------------------------------ 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 [email protected] https://lists.sourceforge.net/lists/listinfo/emacs-app-dev-
