* bug#7765: another crash on mac os x
@ 2010-12-31 18:31 emacs user
2010-12-31 22:00 ` Eli Zaretskii
0 siblings, 1 reply; 3+ messages in thread
From: emacs user @ 2010-12-31 18:31 UTC (permalink / raw)
To: 7765
[-- Attachment #1: Type: text/plain, Size: 1362 bytes --]
Another crash on Mac OS X:
This time I compile with -g only, no optimization, start emacs and
then VM to read my inbox (named RMAIL). Emacs crashes mid-way during
the processing of the inbox. I cannot reproduce this without my setup
and mail files, but am happy to do tests given detailed novice-level
instructions. Am attaching a backtrace. Cheers, E
In GNU Emacs 24.0.50.1 (x86_64-apple-darwin10.5.0, NS apple-appkit-1038.35)
of 2010-12-31 on.local
Windowing system distributor `Apple', version 10.3.1038
configured using `configure '--with-ns' '--without-x' 'CC=gcc' 'CFLAGS=-g''
Important settings:
value of $LC_ALL: nil
value of $LC_COLLATE: C
value of $LC_CTYPE: nil
value of $LC_MESSAGES: nil
value of $LC_MONETARY: nil
value of $LC_NUMERIC: nil
value of $LC_TIME: nil
value of $LANG: nil
value of $XMODIFIERS: nil
locale-coding-system: nil
default enable-multibyte-characters: t
Major mode: Fundamental
Minor modes in effect:
delete-selection-mode: t
display-time-mode: t
auto-image-file-mode: t
tooltip-mode: t
mouse-wheel-mode: t
tool-bar-mode: t
menu-bar-mode: t
file-name-shadow-mode: t
global-font-lock-mode: t
font-lock-mode: t
blink-cursor-mode: t
auto-composition-mode: t
auto-encryption-mode: t
auto-compression-mode: t
line-number-mode: t
transient-mark-mode: t
abbrev-mode: t
[-- Attachment #2: t --]
[-- Type: application/octet-stream, Size: 10603 bytes --]
Last login: Mon Dec 27 17:56:34 on console
$ cd /usr/local/emacs/trunk/src/
$ 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-3xISIt/org.x:0
TERM = xterm-color
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: 0x00007fff5f3aefd8
0x000000010019f60e in mark_object (arg=Cannot access memory at address 0x7fff5f3aefd8
) at alloc.c:5286
5286 {
(gdb) xbacktrace full
"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.
(0x5fbfc070)
"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.
(0x5fbfc868)
"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.
(0x5fbfcd98)
"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.
(0x5fbfd200)
"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.
(0x5fbfd8c0)
"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.
(0x5fbfdcc0)
"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.
(0x5fbfe0f8)
(gdb) backtrace full
#0 0x00007fff84091704 in malloc_gdb_po_unsafe ()
No symbol table info available.
Lisp Backtrace:
"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.
(0x5fbfc070)
"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.
(0x5fbfc868)
"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.
(0x5fbfcd98)
"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.
(0x5fbfd200)
"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.
(0x5fbfd8c0)
"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.
(0x5fbfdcc0)
"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.
(0x5fbfe0f8)
(gdb) where
#0 0x00007fff84091704 in malloc_gdb_po_unsafe ()
Lisp Backtrace:
"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.
(0x5fbfc070)
"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.
(0x5fbfc868)
"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.
(0x5fbfcd98)
"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.
(0x5fbfd200)
"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.
(0x5fbfd8c0)
"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.
(0x5fbfdcc0)
"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.
(0x5fbfe0f8)
(gdb)
#0 0x00007fff84091704 in malloc_gdb_po_unsafe ()
Lisp Backtrace:
"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.
(0x5fbfc070)
"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.
(0x5fbfc868)
"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.
(0x5fbfcd98)
"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.
(0x5fbfd200)
"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.
(0x5fbfd8c0)
"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.
(0x5fbfdcc0)
"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.
(0x5fbfe0f8)
(gdb) where
#0 0x00007fff84091704 in malloc_gdb_po_unsafe ()
Lisp Backtrace:
"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.
(0x5fbfc070)
"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.
(0x5fbfc868)
"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.
(0x5fbfcd98)
"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.
(0x5fbfd200)
"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.
(0x5fbfd8c0)
"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.
(0x5fbfdcc0)
"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.
(0x5fbfe0f8)
(gdb)
^ permalink raw reply [flat|nested] 3+ messages in thread
* bug#7765: another crash on mac os x
2010-12-31 18:31 bug#7765: another crash on mac os x emacs user
@ 2010-12-31 22:00 ` Eli Zaretskii
2011-01-01 0:41 ` emacs user
0 siblings, 1 reply; 3+ messages in thread
From: Eli Zaretskii @ 2010-12-31 22:00 UTC (permalink / raw)
To: emacs user; +Cc: 7765
> Date: Fri, 31 Dec 2010 20:31:31 +0200
> From: emacs user <user.emacs@gmail.com>
> 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".
^ permalink raw reply [flat|nested] 3+ messages in thread
* bug#7765: another crash on mac os x
2010-12-31 22:00 ` Eli Zaretskii
@ 2011-01-01 0:41 ` emacs user
0 siblings, 0 replies; 3+ messages in thread
From: emacs user @ 2011-01-01 0:41 UTC (permalink / raw)
To: Eli Zaretskii; +Cc: 7765
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 <eliz@gnu.org> wrote:
>> Date: Fri, 31 Dec 2010 20:31:31 +0200
>> From: emacs user <user.emacs@gmail.com>
>> 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".
>
^ permalink raw reply [flat|nested] 3+ messages in thread
end of thread, other threads:[~2011-01-01 0:41 UTC | newest]
Thread overview: 3+ messages (download: mbox.gz follow: Atom feed
-- links below jump to the message on this page --
2010-12-31 18:31 bug#7765: another crash on mac os x emacs user
2010-12-31 22:00 ` Eli Zaretskii
2011-01-01 0:41 ` emacs user
Code repositories for project(s) associated with this public inbox
https://git.savannah.gnu.org/cgit/emacs.git
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).