From: "Juanma Barranquero" <lekktu@gmail.com>
To: "Emacs Bug Tracker" <submit@emacsbugs.donarmstrong.com>
Subject: bug#872: Crash displaying byte-code
Date: Wed, 3 Sep 2008 18:06:12 +0200 [thread overview]
Message-ID: <f7ccd24b0809030906y723345abj2a9db4a914f7345b@mail.gmail.com> (raw)
emacs -Q
M-x ielm <RET>
then typing
(let ((standard-output (current-buffer)))
(setq unibyte-display-via-language-environment t)
(set-buffer-multibyte nil)
(backtrace))
makes Emacs crash on Windows.
Notes:
- If Emacs is run from inside GDB, it "hangs" for a while and finally
crashes.
- If run from the command-line, after doing the above it crashes
immediately; the DrMingw backtrace is a bit different.
- It only happens with an optimized build.
- All the above steps are required, including executing the `let'
from inside IELM. In fact, the crash happens while IELM is trying to
display byte-code("...")
It apparently started happening after this change:
2008-04-09 Jason Rumney <address@hidden>
* w32term.c (w32_compute_glyph_string_overhangs): Compute overhangs
for new font backend and composite cases.
emacs-devel discussion:
http://lists.gnu.org/archive/html/emacs-devel/2008-08/msg00236.html
next reply other threads:[~2008-09-03 16:06 UTC|newest]
Thread overview: 27+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <494134D7.9000502@f2s.com>
2008-09-03 16:06 ` Juanma Barranquero [this message]
2008-12-11 15:45 ` bug#872: marked as done (Crash displaying byte-code) Emacs bug Tracking System
2008-10-16 14:52 ` bug#1179: Emacs on Windows hangs displaying unibyte strings Juanma Barranquero
2008-10-17 11:48 ` Juanma Barranquero
2008-10-17 11:55 ` Processed: " Emacs bug Tracking System
2008-10-17 13:01 ` Eli Zaretskii
2008-10-17 13:32 ` Juanma Barranquero
2008-10-17 14:01 ` Eli Zaretskii
2008-10-17 14:14 ` Juanma Barranquero
2008-12-11 15:45 ` bug#1179: marked as done (Emacs on Windows hangs displaying unibyte strings) Emacs bug Tracking System
2008-11-28 4:15 ` bug#1446: 23.0.60; GNU Emacs 23.0.60.1 (i386-mingw-nt5.1.2600) of 2008-11-28 crash on "C-h b" Feng li
2008-12-11 15:45 ` bug#1446: marked as done (23.0.60; GNU Emacs 23.0.60.1 (i386-mingw-nt5.1.2600) of 2008-11-28 crash on "C-h b") Emacs bug Tracking System
2008-11-28 4:33 ` bug#1447: 23.0.60; emacs crash Feng li
2008-12-11 15:45 ` bug#1447: marked as done (23.0.60; emacs crash) Emacs bug Tracking System
2008-11-28 5:15 ` bug#1448: 23.0.60; update to cvs emacs crash report Feng li
2008-11-28 9:25 ` Juanma Barranquero
2008-11-28 10:56 ` Eli Zaretskii
2008-11-28 11:23 ` Juanma Barranquero
2008-11-28 12:06 ` Eli Zaretskii
2008-11-28 12:08 ` Juanma Barranquero
2008-11-30 22:11 ` Feng Li
2008-11-30 23:03 ` Juanma Barranquero
2008-12-04 2:47 ` Feng Li
2008-12-04 8:44 ` Juanma Barranquero
2008-12-04 13:31 ` Stefan Monnier
2008-12-04 14:51 ` Juanma Barranquero
2008-12-11 15:45 ` bug#1448: marked as done (23.0.60; update to cvs emacs crash report) Emacs bug Tracking System
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=f7ccd24b0809030906y723345abj2a9db4a914f7345b@mail.gmail.com \
--to=lekktu@gmail.com \
--cc=872@emacsbugs.donarmstrong.com \
--cc=submit@emacsbugs.donarmstrong.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).