From: Eli Zaretskii <eliz@gnu.org>
To: Gregor Zattler <grfz@gmx.de>
Cc: bug-gnu-emacs@gnu.org, notmuch@notmuchmail.org
Subject: Re: bug#59147: 29.0.50; dispnew.c:1456: Emacs fatal error: assertion failed: row >= 0 && row < matrix->nrows
Date: Wed, 09 Nov 2022 15:21:31 +0200 [thread overview]
Message-ID: <831qqcuuuc.fsf@gnu.org> (raw)
In-Reply-To: <87o7tg718m.fsf@no.workgroup> (message from Gregor Zattler on Wed, 09 Nov 2022 13:37:13 +0100)
> From: Gregor Zattler <grfz@gmx.de>
> Date: Wed, 09 Nov 2022 13:37:13 +0100
>
> Dear Emacs and notmuch developers, lately Emacs often
> hangs/crashes/stops while I'm working. I cannot reproduce
> with emacs -Q, because I need at least org-mode and notmuch
> for work.
>
> Anyway, here is a (x)backtrace from an unoptimized, rather
> current build, please tell me, if this is helpful or if I
> should not send such backtraces (I myself cannot read them,
> I'm happy to answer questions, in this case the Emacs
> process is still in gdb till max tomorrow 08:00 UTC, then I
> have to shutdown the laptop):
>
> dispnew.c:1456: Emacs fatal error: assertion failed: row >= 0 && row < matrix->nrows
>
> Thread 1 "emacs" hit Breakpoint 1, terminate_due_to_signal (sig=6, backtrace_limit=2147483647) at emacs.c:421
> 421 {
> (gdb) bt
> #0 terminate_due_to_signal (sig=6, backtrace_limit=2147483647) at emacs.c:421
> #1 0x000055555581cae5 in die (msg=0x55555598b4e8 "row >= 0 && row < matrix->nrows", file=0x55555598b293 "dispnew.c", line=1456) at alloc.c:7692
> #2 0x000055555559d310 in matrix_row (matrix=0x55555d44d470, row=8) at dispnew.c:1456
What does the below produce:
(gdb) frame 2
(gdb) p matrix->nrows
next prev parent reply other threads:[~2022-11-09 13:30 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-11-09 12:37 29.0.50; dispnew.c:1456: Emacs fatal error: assertion failed: row >= 0 && row < matrix->nrows Gregor Zattler
2022-11-09 13:21 ` Eli Zaretskii [this message]
2022-11-09 13:49 ` bug#59147: " Gregor Zattler
2022-11-09 14:06 ` Eli Zaretskii
2022-11-09 14:35 ` Gregor Zattler
2022-11-09 14:43 ` Eli Zaretskii
2022-11-09 15:27 ` Gregor Zattler
2022-11-18 11:38 ` Gregor Zattler
2022-11-18 12:03 ` 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
List information: https://notmuchmail.org/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=831qqcuuuc.fsf@gnu.org \
--to=eliz@gnu.org \
--cc=bug-gnu-emacs@gnu.org \
--cc=grfz@gmx.de \
--cc=notmuch@notmuchmail.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://yhetil.org/notmuch.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).