GNU bug report logs - #7765
another crash on mac os x

Previous Next

To add a comment to this bug, you must first unarchive it, by sending
a message to control AT debbugs.gnu.org, with unarchive 7765 in the body.
You can then email your comments to 7765 AT debbugs.gnu.org in the normal way.

Toggle the display of automated, internal messages from the tracker.

Message #5 received at submit <at> debbugs.gnu.org (full text, mbox):

From: emacs user <user.emacs <at> gmail.com>
To: bug-gnu-emacs <at> gnu.org
Subject: another crash on mac os x
Date: Fri, 31 Dec 2010 20:31:31 +0200

[Message part 1 (text/plain, inline)]

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

[t (application/octet-stream, attachment)]

Message #8 received at 7765 <at> debbugs.gnu.org (full text, mbox):

From: Eli Zaretskii <eliz <at> gnu.org>
To: emacs user <user.emacs <at> gmail.com>
Cc: 7765 <at> debbugs.gnu.org
Subject: Re: bug#7765: another crash on mac os x
Date: Sat, 01 Jan 2011 00:00:11 +0200

> Date: Fri, 31 Dec 2010 20:31:31 +0200
> From: emacs user <user.emacs <at> 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".

Message #11 received at 7765 <at> debbugs.gnu.org (full text, mbox):

From: emacs user <user.emacs <at> gmail.com>
To: Eli Zaretskii <eliz <at> gnu.org>
Cc: 7765 <at> debbugs.gnu.org
Subject: Re: bug#7765: another crash on mac os x
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 <eliz <at> gnu.org> wrote:
>> Date: Fri, 31 Dec 2010 20:31:31 +0200
>> From: emacs user <user.emacs <at> 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".
>

Message #18 received at 7765 <at> debbugs.gnu.org (full text, mbox):

From: Alan Third <alan <at> idiocy.org>
To: Konrad Hinsen <konrad.hinsen <at> fastmail.net>
Cc: 7765 <at> debbugs.gnu.org, 11997 <at> debbugs.gnu.org,
 emacs user <user.emacs <at> gmail.com>
Subject: Re: bug#11997: 24.1.50; Crash under MacOS X
Date: Sun, 17 Jul 2016 21:32:26 +0100

Konrad Hinsen <konrad.hinsen <at> fastmail.net> writes:

> Emacs crashed while I was reading my mail using ViewMail. This happens
> to me about once per month. The gdb traceback is attached. My Emacs
> was compiled from trunk in the Bazaar repository, updated on July 19th
> 2012.

Hi, sorry nobody's got back to you about these crashes before now. Are
either of you still getting them?

-- 
Alan Third

Message #23 received at 7765 <at> debbugs.gnu.org (full text, mbox):

From: Konrad Hinsen <konrad.hinsen <at> fastmail.net>
To: Alan Third <alan <at> idiocy.org>
Cc: 7765 <at> debbugs.gnu.org, 11997 <at> debbugs.gnu.org,
 emacs user <user.emacs <at> gmail.com>
Subject: Re: bug#11997: 24.1.50; Crash under MacOS X
Date: Tue, 02 Aug 2016 08:58:47 +0200

Alan Third <alan <at> idiocy.org> writes:

> Konrad Hinsen <konrad.hinsen <at> fastmail.net> writes:
>
>> Emacs crashed while I was reading my mail using ViewMail. This happens
>> to me about once per month. The gdb traceback is attached. My Emacs
>> was compiled from trunk in the Bazaar repository, updated on July 19th
>> 2012.
>
> Hi, sorry nobody's got back to you about these crashes before now. Are
> either of you still getting them?

I switched from VM to notmuch a year ago, but I stopped noticing those
crashes long before, so I assume the bug has been fixed.

Konrad.

Message #28 received at 7765-done <at> debbugs.gnu.org (full text, mbox):

From: Alan Third <alan <at> idiocy.org>
To: Konrad Hinsen <konrad.hinsen <at> fastmail.net>
Cc: 7765-done <at> debbugs.gnu.org, 11997 <at> debbugs.gnu.org,
 emacs user <user.emacs <at> gmail.com>
Subject: Re: bug#11997: 24.1.50; Crash under MacOS X
Date: Thu, 11 Aug 2016 19:47:14 +0100

Konrad Hinsen <konrad.hinsen <at> fastmail.net> writes:

> Alan Third <alan <at> idiocy.org> writes:
>
>> Konrad Hinsen <konrad.hinsen <at> fastmail.net> writes:
>>
>>> Emacs crashed while I was reading my mail using ViewMail. This happens
>>> to me about once per month. The gdb traceback is attached. My Emacs
>>> was compiled from trunk in the Bazaar repository, updated on July 19th
>>> 2012.
>>
>> Hi, sorry nobody's got back to you about these crashes before now. Are
>> either of you still getting them?
>
> I switched from VM to notmuch a year ago, but I stopped noticing those
> crashes long before, so I assume the bug has been fixed.

Thanks. I'm going to close this bug report, but if anyone is still
experiencing the crashes, please let us know or re-open the report.
-- 
Alan Third

Previous Next

GNU bug tracking system
Copyright (C) 1999 Darren O. Benham, 1997,2003 nCipher Corporation Ltd, 1994-97 Ian Jackson.