From: Eli Zaretskii <eliz@gnu.org>
To: Juanma Barranquero <lekktu@gmail.com>
Cc: fengli@blackmagic-design.com, 1448@emacsbugs.donarmstrong.com
Subject: bug#1448: 23.0.60; update to cvs emacs crash report
Date: Fri, 28 Nov 2008 14:06:10 +0200 [thread overview]
Message-ID: <u4p1sgiml.fsf@gnu.org> (raw)
In-Reply-To: <f7ccd24b0811280323o47f2c541vecee420687df6eb4@mail.gmail.com>
> Date: Fri, 28 Nov 2008 12:23:33 +0100
> From: "Juanma Barranquero" <lekktu@gmail.com>
> Cc: 1448@emacsbugs.donarmstrong.com, "Feng li" <fengli@blackmagic-design.com>
>
> > Note that `s' is allocated via `alloca' in BUILD_CHAR_GLYPH_STRINGS,
> > which is called by BUILD_GLYPH_STRINGS, which in turn is called by
> > `draw_glyphs' at line 20332 in frame #1:
>
> Sorry, I fail to understand what you are trying to say.
I was just trying to add more info about where `s' comes from. Since
it comes from a call to `alloca', which is a compiler built-in with
GCC, it could be a compiler bug
> I've suspected that alloca'd memory is related to the crash, but I
> don't see how.
Neither do I.
next prev parent reply other threads:[~2008-11-28 12: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 ` bug#872: Crash displaying byte-code Juanma Barranquero
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 [this message]
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
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=u4p1sgiml.fsf@gnu.org \
--to=eliz@gnu.org \
--cc=1448@emacsbugs.donarmstrong.com \
--cc=fengli@blackmagic-design.com \
--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 external index
https://git.savannah.gnu.org/cgit/emacs.git
https://git.savannah.gnu.org/cgit/emacs/org-mode.git
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.