From: Juanma Barranquero <lekktu@gmail.com>
To: Drew Adams <drew.adams@oracle.com>
Cc: 16908@debbugs.gnu.org
Subject: bug#16908: 24.3.50; emacs_backtrace.txt
Date: Fri, 28 Feb 2014 17:14:27 +0100 [thread overview]
Message-ID: <CAAeL0SS7Fk1xtgDEog3Ktb4mFoUvzb+zK1nVOZ==YciM24AjHA@mail.gmail.com> (raw)
In-Reply-To: <a480df01-d7af-4d9e-ae04-3570c2bc3a22@default>
??
??:0
w32_backtrace at w32fns.c:8431
emacs_abort at w32fns.c:8463
terminate_due_to_signal at emacs.c:378
die at alloc.c:6761
compact_small_strings at alloc.c:1960
sweep_strings at alloc.c:1890
gc_sweep at alloc.c:6333
Fgarbage_collect at alloc.c:5572
maybe_gc at lisp.h:4518
exec_byte_code at bytecode.c:954
funcall_lambda at eval.c:3049
Ffuncall at eval.c:2864
exec_byte_code at bytecode.c:919
Fbyte_code at bytecode.c:482
eval_sub at eval.c:2191
internal_lisp_condition_case at eval.c:1323
exec_byte_code at bytecode.c:1169
funcall_lambda at eval.c:3049
Ffuncall at eval.c:2864
Fapply at eval.c:2354
Ffuncall at eval.c:2796
exec_byte_code at bytecode.c:919
funcall_lambda at eval.c:2983
Ffuncall at eval.c:2864
exec_byte_code at bytecode.c:919
funcall_lambda at eval.c:3049
Ffuncall at eval.c:2864
exec_byte_code at bytecode.c:919
funcall_lambda at eval.c:2983
Ffuncall at eval.c:2864
exec_byte_code at bytecode.c:919
funcall_lambda at eval.c:2983
Ffuncall at eval.c:2864
exec_byte_code at bytecode.c:919
funcall_lambda at eval.c:2983
Ffuncall at eval.c:2864
exec_byte_code at bytecode.c:919
funcall_lambda at eval.c:3049
Ffuncall at eval.c:2864
Fapply at eval.c:2354
Ffuncall at eval.c:2796
exec_byte_code at bytecode.c:919
funcall_lambda at eval.c:2983
Ffuncall at eval.c:2864
exec_byte_code at bytecode.c:919
funcall_lambda at eval.c:2983
Ffuncall at eval.c:2864
exec_byte_code at bytecode.c:919
funcall_lambda at eval.c:2983
Ffuncall at eval.c:2864
exec_byte_code at bytecode.c:919
funcall_lambda at eval.c:2983
Ffuncall at eval.c:2864
Fcall_interactively at callint.c:836
Ffuncall at eval.c:2822
exec_byte_code at bytecode.c:919
funcall_lambda at eval.c:2983
Ffuncall at eval.c:2864
call1 at eval.c:2614
command_loop_1 at keyboard.c:1556
internal_condition_case at eval.c:1354
command_loop_2 at keyboard.c:1174
??
??:0
next prev parent reply other threads:[~2014-02-28 16:14 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-02-28 15:57 bug#16908: 24.3.50; emacs_backtrace.txt Drew Adams
2014-02-28 16:14 ` Juanma Barranquero [this message]
2014-03-01 6:55 ` Eli Zaretskii
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='CAAeL0SS7Fk1xtgDEog3Ktb4mFoUvzb+zK1nVOZ==YciM24AjHA@mail.gmail.com' \
--to=lekktu@gmail.com \
--cc=16908@debbugs.gnu.org \
--cc=drew.adams@oracle.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).