From: Dani Moncayo <dmoncayo@gmail.com>
To: 15565@debbugs.gnu.org
Subject: bug#15565: 24.3.50; emacs_backtrace
Date: Tue, 8 Oct 2013 22:04:38 +0200 [thread overview]
Message-ID: <CAH8Pv0he6H497bQHvaX7rLB5o+5LDFMd6wkMfchCcwZvA5OzPA@mail.gmail.com> (raw)
I've just bootstrapped the latest trunk, and it crashes very easily.
For example:
emacs -Q
C-h r
This is the backtrace I get:
??
??:0
??
??:0
w32_backtrace at w32fns.c:7965
emacs_abort at w32fns.c:7997
terminate_due_to_signal at emacs.c:376
die at alloc.c:6605
x_free_gc at xfaces.c:632
free_realized_face at xfaces.c:4049
free_realized_faces at xfaces.c:4221
free_all_realized_faces at xfaces.c:4255
init_iterator at xdisp.c:2665
resize_mini_window at xdisp.c:10471
display_echo_area_1 at xdisp.c:10357
with_echo_area_buffer at xdisp.c:10147
display_echo_area at xdisp.c:10327
echo_area_display at xdisp.c:10831
message3_nolog at xdisp.c:9828
message3 at xdisp.c:9774
message1 at xdisp.c:9847
Fmessage at editfns.c:3442
Ffuncall at eval.c:2770
exec_byte_code at bytecode.c:919
funcall_lambda at eval.c:3023
Ffuncall at eval.c:2838
exec_byte_code at bytecode.c:919
funcall_lambda at eval.c:3023
Ffuncall at eval.c:2838
exec_byte_code at bytecode.c:919
funcall_lambda at eval.c:3023
Ffuncall at eval.c:2838
exec_byte_code at bytecode.c:919
funcall_lambda at eval.c:3023
Ffuncall at eval.c:2838
exec_byte_code at bytecode.c:919
funcall_lambda at eval.c:3023
Ffuncall at eval.c:2838
exec_byte_code at bytecode.c:919
funcall_lambda at eval.c:3023
Ffuncall at eval.c:2838
exec_byte_code at bytecode.c:919
funcall_lambda at eval.c:3023
Ffuncall at eval.c:2838
exec_byte_code at bytecode.c:919
funcall_lambda at eval.c:3023
Ffuncall at eval.c:2838
exec_byte_code at bytecode.c:919
funcall_lambda at eval.c:3023
Ffuncall at eval.c:2838
exec_byte_code at bytecode.c:919
funcall_lambda at eval.c:3023
Ffuncall at eval.c:2838
exec_byte_code at bytecode.c:919
funcall_lambda at eval.c:3023
Ffuncall at eval.c:2838
apply1 at eval.c:2555
Fcall_interactively at callint.c:378
Ffuncall at eval.c:2796
exec_byte_code at bytecode.c:919
funcall_lambda at eval.c:2957
Ffuncall at eval.c:2838
call1 at eval.c:2588
command_loop_1 at keyboard.c:1561
internal_condition_case at eval.c:1331
command_loop_2 at keyboard.c:1162
??
??:0
In GNU Emacs 24.3.50.1 (i686-pc-mingw32)
of 2013-10-08 on LEG570
Bzr revision: 114584 eliz@gnu.org-20131008190640-26yo36k2fe8lgk8i
Windowing system distributor `Microsoft Corp.', version 6.1.7601
Configured using:
`configure --enable-checking 'CFLAGS=-O0 -g3' CPPFLAGS=-DGLYPH_DEBUG=1'
Important settings:
value of $LANG: ENU
locale-coding-system: cp1252
default enable-multibyte-characters: t
--
Dani Moncayo
next reply other threads:[~2013-10-08 20:04 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-10-08 20:04 Dani Moncayo [this message]
2013-10-08 20:11 ` bug#15565: 24.3.50; emacs_backtrace Eli Zaretskii
2013-10-08 20:53 ` Dani Moncayo
2013-10-09 14:58 ` 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=CAH8Pv0he6H497bQHvaX7rLB5o+5LDFMd6wkMfchCcwZvA5OzPA@mail.gmail.com \
--to=dmoncayo@gmail.com \
--cc=15565@debbugs.gnu.org \
/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).