all messages for Emacs-related lists mirrored at yhetil.org
 help / color / mirror / code / Atom feed
From: Eli Zaretskii <eliz@gnu.org>
To: Juanma Barranquero <lekktu@gmail.com>,
	Stefan Monnier <monnier@iro.umontreal.ca>
Cc: 17318@debbugs.gnu.org
Subject: bug#17318: 24.4.50; emacs_backtrace.txt
Date: Fri, 25 Apr 2014 10:05:14 +0300	[thread overview]
Message-ID: <83ppk5q47p.fsf@gnu.org> (raw)
In-Reply-To: <CAAeL0SQR6Ye=ws_z2Ykipx_gSEgjmsxVf_5cS1h3Gri3u+RUiA@mail.gmail.com>

> From: Juanma Barranquero <lekktu@gmail.com>
> Date: Thu, 24 Apr 2014 22:13:54 +0200
> Cc: 17318@debbugs.gnu.org
> 
> mark_interval at alloc.c:1333

> w32_backtrace at w32fns.c:8476
> emacs_abort at w32fns.c:8508
> terminate_due_to_signal at emacs.c:382
> die at alloc.c:6955
> make_natnum at lisp.h:729
> Flength at fns.c:119
> concat at fns.c:524
> Fcopy_sequence at fns.c:456
> compile_pattern_1 at search.c:164
> compile_pattern at search.c:245
> fast_string_match at search.c:478
> Ffind_file_name_handler at fileio.c:372
> Fexpand_file_name at fileio.c:903
> Fdo_auto_save at fileio.c:5553
> shut_down_emacs at emacs.c:2033
> terminate_due_to_signal at emacs.c:366
> handle_fatal_signal at sysdep.c:1630
> deliver_thread_signal at sysdep.c:1604
> deliver_fatal_thread_signal at sysdep.c:1642
> ?? at crt1.c:0

Looks like a new one.  The first line shows where the original crash
happened, the rest are a secondary crash when Emacs tried to shut down
itself.

Stefan, could this be related to your latest changes in intervals.c?





  reply	other threads:[~2014-04-25  7:05 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-04-23  3:02 bug#17318: 24.4.50; emacs_backtrace.txt Drew Adams
2014-04-24 20:13 ` Juanma Barranquero
2014-04-25  7:05   ` Eli Zaretskii [this message]
2014-04-25 13:43     ` Stefan Monnier
2014-04-25 14:11       ` Eli Zaretskii
2015-09-10 16:29 ` bug#17318: Glenn Morris

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=83ppk5q47p.fsf@gnu.org \
    --to=eliz@gnu.org \
    --cc=17318@debbugs.gnu.org \
    --cc=lekktu@gmail.com \
    --cc=monnier@iro.umontreal.ca \
    /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.