Re: bug#59147: 29.0.50; dispnew.c:1456: Emacs fatal error: assertion failed: row >= 0 && row < matrix->nrows
close 59147 thanks > From: Gregor Zattler > Cc: bug-gnu-em...@gnu.org, notmuch@notmuchmail.org > Date: Fri, 18 Nov 2022 12:38:51 +0100 > > Hi Eli, > * Eli Zaretskii [2022-11-09; 16:43 +02]: > > OK. I installed a possible fix. Can you update from Git, rebuild, > > and see if it eliminates the assertions? > > I did so same day. Before the problem was rather frequent. > > But since the new build I did not encounter similar > problems. Thanks, so I'm closing this bug. If you see this assertion again, please let us know. ___ notmuch mailing list -- notmuch@notmuchmail.org To unsubscribe send an email to notmuch-le...@notmuchmail.org
Re: bug#59147: 29.0.50; dispnew.c:1456: Emacs fatal error: assertion failed: row >= 0 && row < matrix->nrows
> From: Gregor Zattler > Cc: bug-gnu-em...@gnu.org, notmuch@notmuchmail.org > Date: Wed, 09 Nov 2022 15:35:01 +0100 > > > The backtrace seems to indicate that it reads from the minibuffer, but > > in that case, does it mean the mini-window was 7-lines high in this > > case? > > quite possible, I have quite a few saved searches which are > presented to me. The hight of the minibuffer also depends > on the frames width. If the frame is half of the width of > my monitor the choices are listed in 6 lines, then there is > a blan line and a final line with a prompt. In fullscreen > it's 3 lines of choices, the blank line and the prompt. > > > Also, can you describe what you do to trigger this assertion > > violation? > > I can do so only on the level of user interaction: I call > notmuch-jump-search via it's key binding which is key chord > prefixed. Then I enter one or more chars to select the > specific saved search I want to perform. It might be > possible that I'm typing faster than Emacs performs this > commands. Emacs hits the assertion with the choices still > visible. I cannot say if it does so after my last key > stroke or in the middel of them. OK. I installed a possible fix. Can you update from Git, rebuild, and see if it eliminates the assertions? ___ notmuch mailing list -- notmuch@notmuchmail.org To unsubscribe send an email to notmuch-le...@notmuchmail.org
Re: bug#59147: 29.0.50; dispnew.c:1456: Emacs fatal error: assertion failed: row >= 0 && row < matrix->nrows
> From: Gregor Zattler > Cc: bug-gnu-em...@gnu.org, notmuch@notmuchmail.org > Date: Wed, 09 Nov 2022 14:49:15 +0100 > > > What does the below produce: > > > > (gdb) frame 2 > > (gdb) p matrix->nrows > > (gdb) frame 2 > #2 0x5559d310 in matrix_row (matrix=0x5d44d470, row=8) at > dispnew.c:1456 > 1456 eassert (row >= 0 && row < matrix->nrows); > (gdb) p matrix->nrows > $1 = 7 > (gdb) Can you describe what does notmuch-jump do and maybe show its code? The backtrace seems to indicate that it reads from the minibuffer, but in that case, does it mean the mini-window was 7-lines high in this case? Also, can you describe what you do to trigger this assertion violation? > While working I got another (x)backtracei, in another emacs > daemon, which I guess is related: It's an exact same problem. ___ notmuch mailing list -- notmuch@notmuchmail.org To unsubscribe send an email to notmuch-le...@notmuchmail.org
Re: bug#59147: 29.0.50; dispnew.c:1456: Emacs fatal error: assertion failed: row >= 0 && row < matrix->nrows
> From: Gregor Zattler
> 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 0x5581cae5 in die (msg=0x5598b4e8 "row >= 0 && row <
> matrix->nrows", file=0x5598b293 "dispnew.c", line=1456) at alloc.c:7692
> #2 0x5559d310 in matrix_row (matrix=0x5d44d470, row=8) at
> dispnew.c:1456
What does the below produce:
(gdb) frame 2
(gdb) p matrix->nrows
___
notmuch mailing list -- notmuch@notmuchmail.org
To unsubscribe send an email to notmuch-le...@notmuchmail.org
Re: bug#35370: notmuch-emacs: avoiding deprecated message-default-charset
> From: Lars Ingebrigtsen > Cc: Noam Postavsky , da...@tethera.net, > notmuch@notmuchmail.org, d...@fifthhorseman.net, 35...@debbugs.gnu.org > Date: Thu, 09 May 2019 14:33:15 -0400 > > Eli Zaretskii writes: > > > I think so, but I'd be happier if someone from the Gnus folks could > > eyeball this patch. > > > > Lars, any comments/objections? > > I think the patch looks OK -- it'll change the behaviour if you have > set enable-multibyte-characters to nil, but... does anybody do that? If they do, it's their funeral. Noam, please go ahead, and thanks. ___ notmuch mailing list notmuch@notmuchmail.org https://notmuchmail.org/mailman/listinfo/notmuch
Re: bug#35370: notmuch-emacs: avoiding deprecated message-default-charset
> From: Noam Postavsky > Cc: Daniel Kahn Gillmor , da...@tethera.net, > notmuch@notmuchmail.org, 35...@debbugs.gnu.org > Date: Tue, 07 May 2019 08:26:59 -0400 > > > Just remove any uses of it. Why are you using it now? > > Should we remove the remaining uses of it from Emacs too? I think so, but I'd be happier if someone from the Gnus folks could eyeball this patch. Lars, any comments/objections? ___ notmuch mailing list notmuch@notmuchmail.org https://notmuchmail.org/mailman/listinfo/notmuch
Re: bug#35370: notmuch-emacs: avoiding deprecated message-default-charset
> From: Daniel Kahn Gillmor > Cc: npost...@gmail.com, da...@tethera.net, notmuch@notmuchmail.org, > 35...@debbugs.gnu.org > Date: Mon, 22 Apr 2019 10:21:25 -0400 > > > Just remove any uses of it. Why are you using it now? > > in notmuch's emacs/notmuch-maildir-fcc.el, as mentioned at the beginning > of this thread: > > https://git.notmuchmail.org/git?p=notmuch;a=blob;f=emacs/notmuch-maildir-fcc.el;h=1551e8b649102ccdfecad9a2ef278949bfb3d702;hb=HEAD#l172 > > If we remove that entry from the (let) block, what are the implications > for users of notmuch who are still using emacs 25? Nothing, I think. But if you don't want to risk problems, you can use it dependent on the Emacs version. ___ notmuch mailing list notmuch@notmuchmail.org https://notmuchmail.org/mailman/listinfo/notmuch
Re: bug#35370: notmuch-emacs: avoiding deprecated message-default-charset
> From: Daniel Kahn Gillmor > Date: Sun, 21 Apr 2019 21:55:38 -0400 > Cc: da...@tethera.net, notmuch@notmuchmail.org, 35...@debbugs.gnu.org > > Do you have any recommendation for how an external emacs module (which > aims to work with at emacs 25 as well at least) should handle this? Just remove any uses of it. Why are you using it now? ___ notmuch mailing list notmuch@notmuchmail.org https://notmuchmail.org/mailman/listinfo/notmuch
