[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
bug#70385: Crash in note_fringe_highlight
From: |
Vladimir Kazanov |
Subject: |
bug#70385: Crash in note_fringe_highlight |
Date: |
Sun, 14 Apr 2024 17:41:05 +0100 |
Eli,
Yes, sure, I'll take a look.
On Sun, 14 Apr 2024 at 17:40, Eli Zaretskii <eliz@gnu.org> wrote:
>
> > From: Juri Linkov <juri@linkov.net>
> > Date: Sun, 14 Apr 2024 19:10:16 +0300
> >
> > Hopefully this backtrace could help to find where is the bug:
> >
> > Thread 1 "emacs" received signal SIGSEGV, Segmentation fault.
> > 0x00005555556120fe in note_fringe_highlight (part=<optimized out>,
> > y=<optimized out>, x=<optimized out>, window=XIL(0x5555564aa62d)) at
> > xdisp.c:35762
> > 35762 struct glyph *glyph = MATRIX_ROW_GLYPH_START (w->current_matrix,
> > vpos);
> >
> > (gdb) bt
> > #0 0x00005555556120fe in note_fringe_highlight (part=<optimized out>,
> > y=<optimized out>, x=<optimized out>, window=XIL(0x5555564aa62d)) at
> > xdisp.c:35762
>
> Can you reproduce at will? 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)
>
> Vladimir, can you please look into this?
--
Regards,
Vladimir Kazanov
bug#70385: Crash in note_fringe_highlight, Vladimir Kazanov, 2024/04/14