bug-gnu-emacs
[Top][All Lists]
Advanced

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

bug#16127: 24.3.50; emacs crashes with macfont_free_entity


From: Stefan Kangas
Subject: bug#16127: 24.3.50; emacs crashes with macfont_free_entity
Date: Fri, 23 Aug 2019 08:13:37 +0200

Alan Third <alan@idiocy.org> writes:

> Darren Hoo <darren.hoo@gmail.com> writes:
>
>> Bzr revno: 115489 brings this crash:
>>
>>  lldb src/emacs
>> Current executable set to 'src/emacs' (x86_64).
>> (lldb) run
>> Process 17619 launched: '/Volumes/disk/emacs/src/emacs' (x86_64)
>> Process 17619 stopped
>> * thread #1: tid = 0x1f0644, 0x00000001001ac8cb emacs`macfont_free_entity 
>> [inlined] XCDR(c=9053142519906304, obj=9053142519906304, n=0) + 4 at 
>> lisp.h:2007, queue = 'com.apple.main-thread, stop reason = EXC_BAD_ACCESS 
>> (code=EXC_I386_GPFLT)
>>     frame #0: 0x00000001001ac8cb emacs`macfont_free_entity [inlined] 
>> XCDR(c=9053142519906304, obj=9053142519906304, n=0) + 4 at lisp.h:2007
>>    2004    XSAVE_POINTER (Lisp_Object obj, int n)
>>    2005    {
>>    2006      eassert (save_type (XSAVE_VALUE (obj), n) == SAVE_POINTER);
>> -> 2007      return XSAVE_VALUE (obj)->data[n].pointer;
>>    2008    }
>>    2009    INLINE void
>>    2010    set_save_pointer (Lisp_Object obj, int n, void *val)
>> (lldb) bt all
>> * thread #1: tid = 0x1f0644, 0x00000001001ac8cb emacs`macfont_free_entity 
>> [inlined] XCDR(c=9053142519906304, obj=9053142519906304, n=0) + 4 at 
>> lisp.h:2007, queue = 'com.apple.main-thread, stop reason = EXC_BAD_ACCESS 
>> (code=EXC_I386_GPFLT)
>>     frame #0: 0x00000001001ac8cb emacs`macfont_free_entity [inlined] 
>> XCDR(c=9053142519906304, obj=9053142519906304, n=0) + 4 at lisp.h:2007
>>     frame #1: 0x00000001001ac8c7 
>> emacs`macfont_free_entity(entity=4353797322) + 23 at macfont.m:2438
>>     frame #2: 0x000000010010910e emacs`Fgarbage_collect [inlined] 
>> cleanup_vector + 84 at alloc.c:2889
>
> Hi, are you still getting this crash with a more up-to-date Emacs?
>
> If so, are there any steps you take to reproduce it?
>
> Thanks!

No reply in three years.  Since this was already tagged unreproducible,
there doesn't seem to be much chance for further progress here.  I'm
therefore closing this bug report.

Thanks,
Stefan Kangas





reply via email to

[Prev in Thread] Current Thread [Next in Thread]