[Top][All Lists]
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: Emacs seems awfully unstable on OS X lately
From: |
Jan Djärv |
Subject: |
Re: Emacs seems awfully unstable on OS X lately |
Date: |
Sun, 16 Sep 2012 10:04:03 +0200 |
Hello.
16 sep 2012 kl. 02:47 skrev Harald Hanche-Olsen <address@hidden>:
> Well, after a day of testing I am inclined to blame revision 109972
> for the instability on OS X. At least, I get crashes with that
> revision and later ones, and so far I haven't seen any crashes with
> earlier revisions. I am running on revision 109971 now. I'll probably
> have to use it for several hours before I can feel confident in this
> conclusion, however.
>
I see craches also, but haven't been able to reproduce it when running with gdb.
> Now I know nothing about Objective C, but the added code in nsterm.m
> doesn't look to me like something that would cause crashes.
>
> However that may be, I managed to provoke a crash with gdb attached,
> but didn't get a useful backtrace; only this:
>
> Program received signal EXC_BAD_ACCESS, Could not access memory.
> Reason: KERN_INVALID_ADDRESS at address: 0x0000000000000011
> 0x00007fff8fc7ae90 in objc_msgSend ()
> (gdb) back
> #0 0x00007fff8fc7ae90 in objc_msgSend ()
> #1 0x0000000000000000 in ?? ()
>
This usually means that an object was freed and after that someone tried to
send it a signal (i.e. method call).
> The backtrace supplied by the OS X crash reporter is a lot more
> informative, I suppose. I supply it below.
>
Actually it is informative, the memory isn't handeled right in this case. I'll
figure out a solution and check in a fix.
Thanks,
Jan D.
> - Harald
>
>
> Thread 0 Crashed:: Dispatch queue: com.apple.main-thread
> 0 libsystem_kernel.dylib 0x00007fff89aa782a __kill + 10
> 1 org.gnu.Emacs 0x00000001000ad57e
> fatal_error_backtrace + 254 (emacs.c:332)
> 2 org.gnu.Emacs 0x00000001000ca6e3 emacs_abort + 19
> 3 org.gnu.Emacs 0x000000010019ca2d ns_term_shutdown +
> 125
> 4 org.gnu.Emacs 0x00000001000adbba shut_down_emacs +
> 250 (emacs.c:2066)
> 5 org.gnu.Emacs 0x00000001000ad531
> fatal_error_backtrace + 177 (emacs.c:315)
> 6 org.gnu.Emacs 0x00000001000afc3e handle_fatal_signal
> + 14
> 7 org.gnu.Emacs 0x00000001000ca953
> handle_on_main_thread + 131 (sysdep.c:1551)
> 8 libsystem_c.dylib 0x00007fff90ebccfa _sigtramp + 26
> 9 libobjc.A.dylib 0x00007fff8fc7ae90 objc_msgSend + 16
> 10 org.gnu.Emacs 0x000000010019a1d2 ns_update_begin +
> 146 (nsterm.m:644)
> 11 org.gnu.Emacs 0x000000010000ade5 update_frame + 213
> (dispnew.c:3187)
> 12 org.gnu.Emacs 0x0000000100042668 redisplay_internal +
> 4696 (xdisp.c:13559)
> 13 org.gnu.Emacs 0x00000001000bd7da read_char + 8410
> (keyboard.c:2496)
> 14 org.gnu.Emacs 0x00000001000c07d1 read_key_sequence +
> 7521
> 15 org.gnu.Emacs 0x00000001000c2278 command_loop_1 +
> 5192 (keyboard.c:1498)
> 16 org.gnu.Emacs 0x0000000100129226
> internal_condition_case + 294 (eval.c:1320)
> 17 org.gnu.Emacs 0x00000001000c0e0e command_loop_2 + 62
> (keyboard.c:1194)
> 18 org.gnu.Emacs 0x000000010012932b internal_catch + 219
> (eval.c:1076)
> 19 org.gnu.Emacs 0x00000001000c28cd recursive_edit_1 +
> 301 (keyboard.c:1158)
> 20 org.gnu.Emacs 0x00000001000e09da read_minibuf + 2346
> (minibuf.c:686)
> 21 org.gnu.Emacs 0x00000001000dde65
> Fread_from_minibuffer + 245 (minibuf.c:988)
> 22 org.gnu.Emacs 0x00000001000ddfce Fread_string + 110
> (minibuf.c:1053)
> 23 org.gnu.Emacs 0x00000001001277c7 Ffuncall + 1047
> (eval.c:2825)
> 24 org.gnu.Emacs 0x000000010015ff08 exec_byte_code +
> 1992 (bytecode.c:898)
> 25 org.gnu.Emacs 0x000000010012aa62 funcall_lambda + 930
> (eval.c:3041)
> 26 org.gnu.Emacs 0x0000000100127857 Ffuncall + 1191
> (eval.c:2858)
> 27 org.gnu.Emacs 0x0000000100124854 Fcall_interactively
> + 6004 (callint.c:853)
> 28 org.gnu.Emacs 0x0000000100127793 Ffuncall + 995
> (eval.c:2816)
> 29 org.gnu.Emacs 0x000000010012abe6 call3 + 38
> (eval.c:2634)
> 30 org.gnu.Emacs 0x00000001000c1475 command_loop_1 +
> 1605 (keyboard.c:1634)
> 31 org.gnu.Emacs 0x0000000100129226
> internal_condition_case + 294 (eval.c:1320)
> 32 org.gnu.Emacs 0x00000001000c0e0e command_loop_2 + 62
> (keyboard.c:1194)
> 33 org.gnu.Emacs 0x000000010012932b internal_catch + 219
> (eval.c:1076)
> 34 org.gnu.Emacs 0x00000001000c2890 recursive_edit_1 +
> 240 (keyboard.c:1173)
> 35 org.gnu.Emacs 0x00000001000b2e9d Frecursive_edit +
> 237 (keyboard.c:857)
> 36 org.gnu.Emacs 0x00000001000afb8c main + 6316
> (emacs.c:1660)
> 37 org.gnu.Emacs 0x00000001000018a4 start + 52
- Re: Emacs seems awfully unstable on OS X lately, (continued)
- Re: Emacs seems awfully unstable on OS X lately, Óscar Fuentes, 2012/09/14
- Re: Emacs seems awfully unstable on OS X lately, Andreas Schwab, 2012/09/15
- Re: Emacs seems awfully unstable on OS X lately, Eli Zaretskii, 2012/09/15
- Re: Emacs seems awfully unstable on OS X lately, Stephen J. Turnbull, 2012/09/15
- Re: Emacs seems awfully unstable on OS X lately, Eli Zaretskii, 2012/09/15
- Re: Emacs seems awfully unstable on OS X lately, Stephen J. Turnbull, 2012/09/15
- Re: Emacs seems awfully unstable on OS X lately, Eli Zaretskii, 2012/09/15
- Re: Emacs seems awfully unstable on OS X lately, Stephen J. Turnbull, 2012/09/15
- Re: Emacs seems awfully unstable on OS X lately, Harald Hanche-Olsen, 2012/09/15
- Re: Emacs seems awfully unstable on OS X lately, Harald Hanche-Olsen, 2012/09/15
- Re: Emacs seems awfully unstable on OS X lately,
Jan Djärv <=
- Re: Emacs seems awfully unstable on OS X lately, Harald Hanche-Olsen, 2012/09/16
- Re: Emacs seems awfully unstable on OS X lately, Jan Djärv, 2012/09/16
- Re: Emacs seems awfully unstable on OS X lately, Harald Hanche-Olsen, 2012/09/16
- Re: Emacs seems awfully unstable on OS X lately, Jan Djärv, 2012/09/16
- Re: Emacs seems awfully unstable on OS X lately, Harald Hanche-Olsen, 2012/09/17
- Re: Emacs seems awfully unstable on OS X lately, Harald Hanche-Olsen, 2012/09/24