unofficial mirror of bug-gnu-emacs@gnu.org 
 help / color / mirror / code / Atom feed
From: Vasilij Schneidermann <mail@vasilij.de>
To: 45156@debbugs.gnu.org
Subject: bug#45156: 28.0.50; Segfault due to glyph_row being set to NULL
Date: Fri, 30 Apr 2021 13:03:22 +0200	[thread overview]
Message-ID: <YIvj+m/ejNmoslFm@odonien.localdomain> (raw)
In-Reply-To: <87v9daaycw.fsf@physik.rwth-aachen.de>

[-- Attachment #1: Type: text/plain, Size: 642 bytes --]

I've run into this bug after upgrading from Emacs 27.1 to 27.2, rebuilt
Emacs with debug symbols and managed to chase it down to a line in
xdisp.c dereferencing a null pointer today. Running `git blame` pointed
me towards this thread. While the bug has been fixed on master and it's
rather tricky to reproduce (it involves at least one third party package
for me and typing a long line at the end of the window that then wraps
around), I'd be inclined to call 27.2 more than just a bugfix release
due to the xdisp.c change introducing this bug. Is there a chance that a
patch can be published for the 27.2 release for downstream maintainers?

[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 488 bytes --]

  parent reply	other threads:[~2021-04-30 11:03 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
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 [this message]
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=YIvj+m/ejNmoslFm@odonien.localdomain \
    --to=mail@vasilij.de \
    --cc=45156@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).