From: Eli Zaretskii <eliz@gnu.org>
To: Juanma Barranquero <lekktu@gmail.com>
Cc: 16414@debbugs.gnu.org
Subject: bug#16414: 24.3.50; emacs_backtrace.txt
Date: Sat, 11 Jan 2014 16:05:10 +0200 [thread overview]
Message-ID: <83ppnyaa21.fsf@gnu.org> (raw)
In-Reply-To: <CAAeL0SSK1T8fk2ghs964rSBCy7op2kV-pPjVuaLvH8SxRCQfdg@mail.gmail.com>
> From: Juanma Barranquero <lekktu@gmail.com>
> Date: Sat, 11 Jan 2014 14:46:10 +0100
> Cc: 16414@debbugs.gnu.org
>
> w32_backtrace at w32fns.c:8386
> emacs_abort at w32fns.c:8418
> terminate_due_to_signal at emacs.c:378
> die at alloc.c:6761
> cleanup_vector at alloc.c:2908
> sweep_vectors at alloc.c:2947
> gc_sweep at alloc.c:6649
> Fgarbage_collect at alloc.c:5572
Thanks. This is a duplicate of #16140.
prev parent reply other threads:[~2014-01-11 14:05 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-01-11 3:14 bug#16414: 24.3.50; emacs_backtrace.txt Drew Adams
2014-01-11 13:46 ` Juanma Barranquero
2014-01-11 14:05 ` 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=83ppnyaa21.fsf@gnu.org \
--to=eliz@gnu.org \
--cc=16414@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).