From: Eli Zaretskii <eliz@gnu.org>
To: Torsten Bronger <bronger@physik.rwth-aachen.de>
Cc: 45156@debbugs.gnu.org
Subject: bug#45156: 28.0.50; Segfault due to glyph_row being set to NULL
Date: Thu, 10 Dec 2020 15:54:55 +0200 [thread overview]
Message-ID: <83tust4vgw.fsf@gnu.org> (raw)
In-Reply-To: <87v9daaycw.fsf@physik.rwth-aachen.de> (message from Torsten Bronger on Thu, 10 Dec 2020 08:55:59 +0100)
> From: Torsten Bronger <bronger@physik.rwth-aachen.de>
> Date: Thu, 10 Dec 2020 08:55:59 +0100
>
> I see Emacs segfaulting when moving the cursor upwards in a LaTeX
> document while tex-fold-mode is active. The starting position of the
> cursor is important.
>
> I placed all files to reproduce the bug at
> <http://wilson.bronger.org/emacs-glyph_row-bug.tar>. The TeX file needs
> to be put in /tmp. tex-fold-mode must be present. Furthermore, place
> .emacs and .emacs.desktop in the proper positions, start current Git
> Emacs, and press the "cursor up" button. Then, Emacs crashes for me.
>
> The subject of this bug is just to give it a name. I do not know
> whether glyph_row is the issue. However, I bisected the problem, and it
> started with commit f425a774, which sets glyph_row to NULL in two
> places. If I revert this commit, the problem is gone.
Ouch! what a terrible blunder! Sorry about that; I see the problem
and am working on a solution.
next prev parent reply other threads:[~2020-12-10 13:54 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-12-10 7:55 bug#45156: 28.0.50; Segfault due to glyph_row being set to NULL Torsten Bronger
2020-12-10 8:35 ` Stefan Kangas
2020-12-10 8:55 ` Torsten Bronger
2020-12-10 14:16 ` Stefan Kangas
2020-12-10 13:54 ` Eli Zaretskii [this message]
2020-12-10 15:12 ` Eli Zaretskii
2020-12-10 21:04 ` Torsten Bronger
2020-12-11 7:56 ` Eli Zaretskii
2021-04-30 11:03 ` Vasilij Schneidermann
2021-04-30 12:41 ` Eli Zaretskii
2021-04-30 13:10 ` Vasilij Schneidermann
2021-04-30 13:36 ` Eli Zaretskii
2021-04-30 15:05 ` Vasilij Schneidermann
2021-04-30 15:12 ` Eli Zaretskii
2021-04-30 14:17 ` Gregory Heytings
2021-04-30 15:03 ` Vasilij Schneidermann
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=83tust4vgw.fsf@gnu.org \
--to=eliz@gnu.org \
--cc=45156@debbugs.gnu.org \
--cc=bronger@physik.rwth-aachen.de \
/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).