From: David Reitter <david.reitter@gmail.com>
To: Eli Zaretskii <eliz@gnu.org>
Cc: 5973@debbugs.gnu.org
Subject: bug#5973: Crash in get_next_display_element
Date: Mon, 19 Apr 2010 13:40:18 -0400 [thread overview]
Message-ID: <4085AF16-E1CB-4A6D-A39C-82E520790237@gmail.com> (raw)
In-Reply-To: <83aaszbbl7.fsf@gnu.org>
On Apr 19, 2010, at 1:23 PM, Eli Zaretskii wrote:
>
> Let's start by finding the immediate reason for the crash. Please
> show the contents of `face', the last argument to FACE_FOR_CHAR in the
> line that crashed.
How do I do that?
It didn't run in gdb, and I don't know how to reproduce the crash.
I just did a search on a year worth of crash logs (47 crashes) and didn't find this specific crash again.
> Also, what kind of signal was it that crashed the program? (The
> backtrace is in some form that I'm not familiar with, so maybe the
> information is already present there.)
Yes:
Exception Type: EXC_BAD_ACCESS (SIGABRT)
Exception Codes: KERN_INVALID_ADDRESS at 0x0000000000000110
>
> Thanks, but I don't think we should fix problems until we understand
> them. In general, it->face_id should index a face that is already
> realized at this point.
Is it possible that this code runs, somehow, after a face got deleted? That, per se, might be the real cause of the bug - but I can only speculate.
As said, the macro is documented to return NULL in some cases, and the code in the same function (below) checks for that case (of course I don't know when such a case can happen). So independently of this particular crash it would be good style to "if (face)" there.
Let me know if I can help in any way.
next prev parent reply other threads:[~2010-04-19 17:40 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-04-19 16:08 bug#5973: Crash in get_next_display_element David Reitter
[not found] ` <handler.5973.B.12716933351499.ack@debbugs.gnu.org>
2010-04-19 16:46 ` bug#5973: Acknowledgement (Crash in get_next_display_element) David Reitter
2010-04-19 17:31 ` Eli Zaretskii
2010-04-19 17:23 ` bug#5973: Crash in get_next_display_element Eli Zaretskii
2010-04-19 17:40 ` David Reitter [this message]
2010-04-19 18:26 ` Eli Zaretskii
2010-04-19 18:39 ` David Reitter
2010-04-19 18:43 ` Eli Zaretskii
2010-04-19 22:46 ` Juanma Barranquero
2010-04-20 8:23 ` Eli Zaretskii
2010-04-20 9:19 ` Juanma Barranquero
2010-04-20 9:56 ` Eli Zaretskii
2010-04-20 10:27 ` Juanma Barranquero
2010-04-20 12:31 ` Eli Zaretskii
2010-04-20 13:36 ` Juanma Barranquero
2010-04-20 13:56 ` Juanma Barranquero
2010-04-20 10:21 ` Eli Zaretskii
2010-04-20 10:33 ` Juanma Barranquero
2010-04-20 12:23 ` 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
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=4085AF16-E1CB-4A6D-A39C-82E520790237@gmail.com \
--to=david.reitter@gmail.com \
--cc=5973@debbugs.gnu.org \
--cc=eliz@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 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.