From: emacs user <user.emacs@gmail.com>
To: 7765@debbugs.gnu.org
Subject: bug#7765: another crash on mac os x
Date: Fri, 31 Dec 2010 20:31:31 +0200 [thread overview]
Message-ID: <AANLkTikkmdsqU3S0ppzDv1tjxHd_AWYgLSYnrWML8CCA@mail.gmail.com> (raw)
[-- 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)
next reply other threads:[~2010-12-31 18:31 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-12-31 18:31 emacs user [this message]
2010-12-31 22:00 ` bug#7765: another crash on mac os x Eli Zaretskii
2011-01-01 0:41 ` emacs user
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=AANLkTikkmdsqU3S0ppzDv1tjxHd_AWYgLSYnrWML8CCA@mail.gmail.com \
--to=user.emacs@gmail.com \
--cc=7765@debbugs.gnu.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
Code repositories for project(s) associated with this external index
https://git.savannah.gnu.org/cgit/emacs.git
https://git.savannah.gnu.org/cgit/emacs/org-mode.git
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.