Re: C-g crash in C-x C-f (OSX Lion)

[Eli Zaretskii]

> Date: Fri, 16 Dec 2011 22:49:49 +0100
> From: Carsten Mattner <address@hidden>
> Cc: address@hidden
> 
> On Fri, Dec 16, 2011 at 10:11 PM, Eli Zaretskii <address@hidden> wrote:
> >> Date: Fri, 16 Dec 2011 21:19:19 +0100
> >> From: Carsten Mattner <address@hidden>
> >> Cc: address@hidden
> >>
> >> > #0  0x9adc5d50 in strlen ()
> >> > #1  0x001e7601 in intern (str=0x0) at lread.c:3707
> >> > #2  0x00283efb in ns_string_to_symbol (t=0x0) at nsselect.m:86
> >> > #3  0x002847ab in ns_handle_selection_request (event=0xbfffef88) at
> >> > nsselect.m:247
> >> >
> >> > vs the below with with the terminal frontend.
> >> >
> >> > Next I will not load evil-mode and see what happens.
> >>
> >> Can these crashes happen due to enabled assertions?
> >
> > No.  Emacs crashes because it tries to compute the length of a string
> > specified by a NULL pointer.  It looks like this happens due to a
> > selection request, but when that request is handled, Emacs tries to
> > intern a name that is a NULL string.
> 
> For the record, I'm not sure this is the original crash I reported
> that happened in the mini-buffer.
> 
> If I enable evil-mode I can reliably make it crash by pressing
> v and then navigating with say } and making a selection.

Since the crash seems to be related to a selection request coming from
outside Emacs, it can happen in any circumstances where you make a
selection or do something that causes Emacs to put text into primary
selection.

So I think these crashes _are_ manifestation of the same problem.