unofficial mirror of bug-gnu-emacs@gnu.org 
 help / color / mirror / code / Atom feed
From: Eli Zaretskii <eliz@gnu.org>
To: Juri Linkov <juri@linkov.net>
Cc: vekazanov@gmail.com, 70385@debbugs.gnu.org
Subject: bug#70385: Crash in note_fringe_highlight
Date: Thu, 18 Apr 2024 14:08:33 +0300	[thread overview]
Message-ID: <86jzkvdj2m.fsf@gnu.org> (raw)
In-Reply-To: <864jc2mvgo.fsf@mail.linkov.net> (message from Juri Linkov on Mon, 15 Apr 2024 19:39:19 +0300)

> From: Juri Linkov <juri@linkov.net>
> Cc: Vladimir Kazanov <vekazanov@gmail.com>,  70385@debbugs.gnu.org
> Date: Mon, 15 Apr 2024 19:39:19 +0300
> 
> > Can you reproduce at will?
> 
> It's not reproducible at will,
> and now I got a new crash.
> 
> > If so, what does the below show in GDB,
> > when Emacs segfaults and GDB kicks in?
> >
> >   (gdb) p w->current_matrix
> >   (gdb) p w->current_matrix->rows
> >   (gdb) p w->current_matrix->nrows
> >   (gdb) p w->window_end_valid
> >   (gdb) p window_outdated (w)
> 
> Thread 1 "emacs" received signal SIGSEGV, Segmentation fault.
> 0x0000555555612343 in note_fringe_highlight (part=<optimized out>, y=<optimized out>, x=<optimized out>, window=XIL(0x55555641d7cd), f=0x55555641d338) at xdisp.c:35774
> 35774	  if (window_outdated (w)
> (gdb) p w->current_matrix
> $6 = (struct glyph_matrix *) 0x55555a95b6f0
> (gdb) p w->current_matrix->rows
> $7 = (struct glyph_row *) 0x555556c14310
> (gdb) p w->current_matrix->nrows
> $8 = 7
> (gdb) p w->window_end_valid
> $9 = false
> (gdb) p window_outdated (w)
> $10 = false

Does the current master branch still crash in note_fringe_highlight?





  reply	other threads:[~2024-04-18 11:08 UTC|newest]

Thread overview: 37+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-04-14 16:10 bug#70385: Crash in note_fringe_highlight Juri Linkov
2024-04-14 16:40 ` Eli Zaretskii
2024-04-14 16:41   ` Vladimir Kazanov
2024-04-15 16:39   ` Juri Linkov
2024-04-18 11:08     ` Eli Zaretskii [this message]
2024-04-18 17:10       ` Juri Linkov
2024-04-18 17:55         ` Eli Zaretskii
2024-04-14 16:40 ` Vladimir Kazanov
2024-04-14 20:13   ` Björn Bidar via Bug reports for GNU Emacs, the Swiss army knife of text editors
     [not found]   ` <87zftv7leb.fsf@>
2024-04-14 20:22     ` Björn Bidar via Bug reports for GNU Emacs, the Swiss army knife of text editors
2024-04-14 20:22     ` Björn Bidar via Bug reports for GNU Emacs, the Swiss army knife of text editors
     [not found]   ` <87edb73d9u.fsf@>
2024-04-15  1:32     ` Po Lu via Bug reports for GNU Emacs, the Swiss army knife of text editors
2024-04-15  6:29       ` Björn Bidar via Bug reports for GNU Emacs, the Swiss army knife of text editors
2024-04-15  6:29       ` Björn Bidar via Bug reports for GNU Emacs, the Swiss army knife of text editors
2024-04-15  6:31       ` Björn Bidar via Bug reports for GNU Emacs, the Swiss army knife of text editors
     [not found]       ` <87bk6b16ii.fsf@>
2024-04-15  6:49         ` Po Lu via Bug reports for GNU Emacs, the Swiss army knife of text editors
2024-04-15 11:06           ` Björn Bidar via Bug reports for GNU Emacs, the Swiss army knife of text editors
     [not found]           ` <661d0a70.0c0a0220.5de8.ce32SMTPIN_ADDED_BROKEN@mx.google.com>
2024-04-15 11:09             ` Vladimir Kazanov
     [not found]           ` <875xwiubq5.fsf@>
2024-04-15 11:26             ` Po Lu via Bug reports for GNU Emacs, the Swiss army knife of text editors
2024-04-15 12:55               ` Eli Zaretskii
2024-04-18 11:06             ` Eli Zaretskii
2024-04-18 14:34               ` Björn Bidar via Bug reports for GNU Emacs, the Swiss army knife of text editors
     [not found]               ` <87edb2buyu.fsf@>
2024-04-18 14:48                 ` Eli Zaretskii
2024-04-15 11:30       ` Eli Zaretskii
2024-04-15 11:57         ` Po Lu via Bug reports for GNU Emacs, the Swiss army knife of text editors
2024-04-15 13:03           ` Eli Zaretskii
2024-04-15 13:58             ` Po Lu via Bug reports for GNU Emacs, the Swiss army knife of text editors
2024-04-15 14:39               ` Eli Zaretskii
2024-04-15 17:04               ` Björn Bidar via Bug reports for GNU Emacs, the Swiss army knife of text editors
2024-04-15 17:04               ` Björn Bidar via Bug reports for GNU Emacs, the Swiss army knife of text editors
     [not found]               ` <87ttk2sgl9.fsf@>
2024-04-15 18:23                 ` Eli Zaretskii
2024-04-15 19:20                   ` Björn Bidar via Bug reports for GNU Emacs, the Swiss army knife of text editors
     [not found]                   ` <87mspuph44.fsf@>
2024-04-16  6:52                     ` Po Lu via Bug reports for GNU Emacs, the Swiss army knife of text editors
2024-04-16 10:56                       ` Björn Bidar via Bug reports for GNU Emacs, the Swiss army knife of text editors
2024-04-15  6:49   ` Juri Linkov
2024-04-15  8:22     ` Vladimir Kazanov
2024-04-15 11:55       ` 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://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=86jzkvdj2m.fsf@gnu.org \
    --to=eliz@gnu.org \
    --cc=70385@debbugs.gnu.org \
    --cc=juri@linkov.net \
    --cc=vekazanov@gmail.com \
    /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).