On Nov 3, 2008, at 3:14 PM, Carsten Bormann wrote:
> On Nov 03 2008, at 18:57, Adrian Robert wrote:
>
>> a crash dialog from OS X
>
> As I mentioned a couple of messages earlier, you don't.
> It seems to me that ns_term_shutdown() simply ignores its argument
> sig, so it always acts as if this was a clean shutdown.
Here's a fix for this that causes a call to abort() when sig is not 0
or SIGTERM. (At this point emacs.c itself has already done what
autosaving etc. it can so should do no harm.) Does this help and
generate a stack trace? If so I'll check it in.
Index: nsterm.m
===================================================================
RCS file: /sources/emacs/emacs/src/nsterm.m,v
retrieving revision 1.39
diff -u -p -r1.39 nsterm.m
--- nsterm.m 28 Nov 2008 05:40:39 -0000 1.39
+++ nsterm.m 7 Dec 2008 16:48:57 -0000
@@ -3984,8 +3984,15 @@ ns_term_shutdown (int sig)
if (STRINGP (Vauto_save_list_file_name))
unlink (SDATA (Vauto_save_list_file_name));
- ns_shutdown_properly = YES;
- [NSApp terminate: NSApp];
+ if (sig == 0 || sig == SIGTERM)
+ {
+ ns_shutdown_properly = YES;
+ [NSApp terminate: NSApp];
+ }
+ else // force a stack trace to happen
+ {
+ abort();
+ }
}
------------------------------------------------------------------------------
SF.Net email is Sponsored by MIX09, March 18-20, 2009 in Las Vegas, Nevada.
The future of the web can't happen without you. Join us at MIX09 to help
pave the way to the Next Web now. Learn more and register at
http://ad.doubleclick.net/clk;208669438;13503038;i?http://2009.visitmix.com/
_______________________________________________
Emacs-app-dev- mailing list
Emacs-app-dev-@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/emacs-app-dev-
