From: Eli Zaretskii <eliz@gnu.org>
To: Juanma Barranquero <lekktu@gmail.com>
Cc: 15044@debbugs.gnu.org
Subject: bug#15044: 24.3.50; emacs_backtrace.txt
Date: Thu, 08 Aug 2013 20:07:26 +0300 [thread overview]
Message-ID: <83pptot8kx.fsf@gnu.org> (raw)
In-Reply-To: <CAAeL0STiRxV58yzQgMkcwihqDbAx11fPQB2YJOnJkPK5ZiCbVQ@mail.gmail.com>
> From: Juanma Barranquero <lekktu@gmail.com>
> Date: Wed, 7 Aug 2013 21:59:09 +0200
> Cc: 15044@debbugs.gnu.org
>
> w32_backtrace at w32fns.c:7990
> emacs_abort at w32fns.c:8022
> Fsignal at eval.c:1475
> xsignal at eval.c:1571
> xsignal1 at eval.c:1586
> Fcheck_coding_system at coding.c:8538
> code_convert_string at coding.c:9434
> code_convert_string_norecord at coding.c:9467
> Fexpand_file_name at fileio.c:1093
> Fexpand_file_name at fileio.c:925
> Fdo_auto_save at fileio.c:5584
> shut_down_emacs at emacs.c:1947
> terminate_due_to_signal at emacs.c:353
> die at alloc.c:6558
> compact_small_strings at alloc.c:1893
> sweep_strings at alloc.c:1823
> gc_sweep at alloc.c:6135
> Fgarbage_collect at alloc.c:5387
> maybe_gc at lisp.h:4339
> exec_byte_code at bytecode.c:739
> funcall_lambda at eval.c:2984
> Ffuncall at eval.c:2865
> exec_byte_code at bytecode.c:905
> funcall_lambda at eval.c:2984
> Ffuncall at eval.c:2865
> exec_byte_code at bytecode.c:905
> funcall_lambda at eval.c:2984
> Ffuncall at eval.c:2865
> call1 at eval.c:2615
> mapcar1 at fns.c:2322
> Fmapcar at fns.c:2392
> Ffuncall at eval.c:2819
> exec_byte_code at bytecode.c:905
> funcall_lambda at eval.c:2984
> Ffuncall at eval.c:2865
> exec_byte_code at bytecode.c:905
> funcall_lambda at eval.c:2984
> Ffuncall at eval.c:2865
> exec_byte_code at bytecode.c:905
> funcall_lambda at eval.c:2984
> Ffuncall at eval.c:2865
> exec_byte_code at bytecode.c:905
> funcall_lambda at eval.c:2984
> Ffuncall at eval.c:2865
> exec_byte_code at bytecode.c:905
> funcall_lambda at eval.c:2984
> Ffuncall at eval.c:2865
> eval_sub at eval.c:2158
> internal_lisp_condition_case at eval.c:1257
> exec_byte_code at bytecode.c:1101
> funcall_lambda at eval.c:2984
> Ffuncall at eval.c:2865
> exec_byte_code at bytecode.c:905
> funcall_lambda at eval.c:2984
> Ffuncall at eval.c:2865
> call3 at eval.c:2646
> Fall_completions at minibuf.c:1487
> eval_sub at eval.c:2196
> internal_lisp_condition_case at eval.c:1257
> exec_byte_code at bytecode.c:1101
> funcall_lambda at eval.c:3050
> Ffuncall at eval.c:2865
This is a crash in GC (followed by another crash in
check-coding-system, but I think the latter is simply because Emacs is
in the middle of a crashed GC).
prev parent reply other threads:[~2013-08-08 17:07 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-08-07 17:53 bug#15044: 24.3.50; emacs_backtrace.txt Drew Adams
2013-08-07 19:59 ` Juanma Barranquero
2013-08-08 17:07 ` Eli Zaretskii [this message]
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
List information: https://www.gnu.org/software/emacs/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=83pptot8kx.fsf@gnu.org \
--to=eliz@gnu.org \
--cc=15044@debbugs.gnu.org \
--cc=lekktu@gmail.com \
/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 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).