Subject: Re: bug#7765: another crash on mac os x

From: emacs user <[email-masked]>
Date: Sat, 1 Jan 2011 02:41:31 +0200

thanks, here it is

 $ gdb /usr/local/emacs/trunk/nextstep/Emacs.app/Contents/MacOS/Emacs
GNU gdb 6.3.50-20050815 (Apple version gdb-1472) (Wed Jul 21 10:53:12 UTC 2010)
Copyright 2004 Free Software Foundation, Inc.
GDB is free software, covered by the GNU General Public License, and you are
welcome to change it and/or distribute copies of it under certain conditions.
Type "show copying" to see the conditions.
There is absolutely no warranty for GDB.  Type "show warranty" for details.
This GDB was configured as "x86_64-apple-darwin"...Reading symbols for
shared libraries ................ done

DISPLAY = /tmp/launch-dbYB4v/org.x:0
TERM = xterm
Breakpoint 1 at 0x4189374bb95c7f
Breakpoint 2 at 0x1001331fe: file sysdep.c, line 836.
(gdb) run
Starting program:
/usr/local/emacs/trunk/nextstep/Emacs.app/Contents/MacOS/Emacs
Reading symbols for shared libraries
.+++++++++++++++..................................................................................
done
Reading symbols for shared libraries . done
Reading symbols for shared libraries . done
Reading symbols for shared libraries . done
Reading symbols for shared libraries . done
Reading symbols for shared libraries . done
Reading symbols for shared libraries . done
Reading symbols for shared libraries . done
Reading symbols for shared libraries . done

Program received signal EXC_BAD_ACCESS, Could not access memory.
Reason: KERN_PROTECTION_FAILURE at address: 0x00007fff5f3aeff8
0x000000010019f606 in mark_object (arg=Cannot access memory at address
0x7fff5f3aefa8
) at alloc.c:5286
5286    {
(gdb) backtrace full
#0  0x000000010019f606 in mark_object (arg=Cannot access memory at
address 0x7fff5f3aefa8
) at alloc.c:5286
        obj = Cannot access memory at address 0x7fff5f3aef68

Lisp Backtrace:
"byte-code"warning: Unable to restore previously selected frame.
Unsafe to call functions on thread 1: function: malloc_gdb_po_unsafe on stack
warning: check_safe_call: could not restore current frame

warning: Canceling operation - malloc lock could be held on current thread.
 (0x5fbfc060)
"vm-read-attributes"Unsafe to call functions on thread 1: function:
malloc_gdb_po_unsafe on stack
warning: check_safe_call: could not restore current frame

warning: Canceling operation - malloc lock could be held on current thread.
 (0x5fbfc858)
"vm-assimilate-new-messages"Unsafe to call functions on thread 1:
function: malloc_gdb_po_unsafe on stack
warning: check_safe_call: could not restore current frame

warning: Canceling operation - malloc lock could be held on current thread.
 (0x5fbfcd88)
"byte-code"Unsafe to call functions on thread 1: function:
malloc_gdb_po_unsafe on stack
warning: check_safe_call: could not restore current frame

warning: Canceling operation - malloc lock could be held on current thread.
 (0x5fbfd1f0)
"vm"Unsafe to call functions on thread 1: function:
malloc_gdb_po_unsafe on stack
warning: check_safe_call: could not restore current frame

warning: Canceling operation - malloc lock could be held on current thread.
 (0x5fbfd8b0)
"vm-my-open-folder-RMAIL"Unsafe to call functions on thread 1:
function: malloc_gdb_po_unsafe on stack
warning: check_safe_call: could not restore current frame

warning: Canceling operation - malloc lock could be held on current thread.
 (0x5fbfdcb0)
"call-interactively"Unsafe to call functions on thread 1: function:
malloc_gdb_po_unsafe on stack
warning: check_safe_call: could not restore current frame

warning: Canceling operation - malloc lock could be held on current thread.
 (0x5fbfe0e8)
(gdb)

On Sat, Jan 1, 2011 at 12:00 AM, Eli Zaretskii <[email-masked]> wrote:
>> Date: Fri, 31 Dec 2010 20:31:31 +0200
>> From: emacs user <[email-masked]>
>> Cc:
>>
>> Another crash on Mac OS X:
>>
>> Program received signal EXC_BAD_ACCESS, Could not access memory.
>> Reason: KERN_PROTECTION_FAILURE at address: 0x00007fff5f3aefd8
>> 0x000000010019f60e in mark_object (arg=Cannot access memory at address 0x7fff5f3aefd8
>> ) at alloc.c:5286
>> 5286  {
>> (gdb) xbacktrace full
>
> That should have been "backtrace full", not "xbacktrace full".
>