Re: EXC_BAD_ACCESS on Mac

[Eli Zaretskii]

> Date: Tue, 18 Jun 2013 11:27:19 +0900 (JST)
> From: Kazu Yamamoto (山本和彦) <address@hidden>
> 
> >> What happens if you apply the following patch and compile
> >> with -DENABLE_CHECKING?
> > 
> > Thanks you for the patch. I compiled Emacs with:
> >     ./configure --with-ns --enable-checking
> > 
> > Let me see what will happen.
> 
> Emacs receives SIGABRT quite often. Two stack traces are attached.
> 
> --Kazu
> 
> #0  0x00007fff93243d46 in __kill ()
> #1  0x00000001000c5a49 in terminate_due_to_signal (sig=6, backtrace_limit=40) 
> at emacs.c:350
> #2  0x00000001000e6d23 in emacs_abort () at sysdep.c:2148
> #3  0x00000001001d921d in ns_term_shutdown (sig=<value temporarily 
> unavailable, due to optimizations>) at nsterm.m:4388
> #4  0x00000001000c60fe in shut_down_emacs (sig=6, stuff=8345) at emacs.c:1951
> #5  0x00000001000c5a0b in terminate_due_to_signal (sig=6, 
> backtrace_limit=2147483647) at emacs.c:334
> #6  0x000000010012c2e3 in die (msg=<value temporarily unavailable, due to 
> optimizations>, file=<value temporarily unavailable, due to optimizations>, 
> line=<value temporarily unavailable, due to optimizations>) at alloc.c:6520
> #7  0x00000001001cc329 in -[EmacsScroller dealloc] (self=<value temporarily 
> unavailable, due to optimizations>, _cmd=0x6) at lisp.h:800
> #8  0x00007fff9074f230 in (anonymous namespace)::AutoreleasePoolPage::pop ()
> #9  0x00007fff8891fd72 in _CFAutoreleasePoolPop ()
> #10 0x00007fff8ed37fbd in -[NSAutoreleasePool release] ()
> #11 0x00000001001dbc01 in ns_read_socket (terminal=0x2099, 
> hold_quit=0x7fff5fbfee60) at nsterm.m:3497
> #12 0x00000001000d382f in gobble_input () at keyboard.c:6850
> #13 0x00000001000d3d95 in swallow_events (do_display=true) at keyboard.c:6771
> #14 0x00000001000050ea in sit_for (timeout=120, display_option=1, 
> reading=true) at dispnew.c:5756
> #15 0x00000001000d82ca in read_char (commandflag=1606414736, 
> map=140734799802768, prev_event=0, used_mouse_menu=0x7fff5fbff190, 
> end_time=0x7fff5fbff190) at keyboard.c:2809

Looks like an entirely different problem.