From: Daniel Clemente <n142857@gmail.com>
To: Eli Zaretskii <eliz@gnu.org>
Cc: 71224@debbugs.gnu.org
Subject: bug#71224: 30.0.50; SIGSEGV in start_display
Date: Tue, 28 May 2024 15:36:05 +0000 [thread overview]
Message-ID: <CAJKAhPDv2AufASSYGr0usG5Ocs-FfKvwGmwKk4HKa_VBAhPxpQ@mail.gmail.com> (raw)
In-Reply-To: <86o78rv499.fsf@gnu.org>
[-- Attachment #1: Type: text/plain, Size: 1640 bytes --]
> If you can still reproduce it, please show the data which is involved
> in the segfault:
I'll do. I haven't been able to reproduce it. But in trying to do it I
found another crash, different code but related functions: bug#71243
I forgot whether in this case (#71224) the stack was also near the stack
limit. Maybe when it's so close to a stack overflow, these SIGSEGV can
happen first.
On Mon, 27 May 2024 at 12:16, Eli Zaretskii <eliz@gnu.org> wrote:
> > From: Daniel Clemente <n142857@gmail.com>
> > Date: Mon, 27 May 2024 11:03:49 +0000
> >
> > I ran a command to constantly open and close emacsclient TTY frames.
> > See details in the previous bug report, bug#71223
> > Copying it for reference:
> > emacs --fg-daemon -Q
> > for j in `seq 300`; do for i in `seq 10`; do urxvt -e emacsclient '-nw'
> '-e' '(dired "~")' &; done; sleep 1 && killall
> > emacsclient; done
> >
> > It crashed with SIGSEGV.
> > This happened only once in the last days, after dozens of attempts
> running that command. I can't reproduce
> > it.
> >
> > Program received signal SIGSEGV, Segmentation fault.
> > start_display (it=0x7fffffb61a60, w=0x555556fa5ae0, pos=...) at
> xdisp.c:3734
> > 3734 row = w->desired_matrix->rows + first_vpos;
>
> If you can still reproduce it, please show the data which is involved
> in the segfault:
>
> (gdb) frame 0
> (gdb) p w->desired_matrix
> (gdb) p w->desired_matrix->nrows
> (gdb) p window_wants_tab_line (w)
> (gdb) p window_wants_header_line (w)
>
> TBH, I'm quite confused to see that line 3734 segfault, because I
> cannot understand how w->desired_matrix can be NULL or bogus.
>
> Thanks.
>
[-- Attachment #2: Type: text/html, Size: 2290 bytes --]
next prev parent reply other threads:[~2024-05-28 15:36 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-05-27 11:03 bug#71224: 30.0.50; SIGSEGV in start_display Daniel Clemente
2024-05-27 12:16 ` Eli Zaretskii
2024-05-28 15:36 ` Daniel Clemente [this message]
2024-05-28 15:55 ` Eli Zaretskii
2024-05-28 16:49 ` Daniel Clemente
2024-05-28 18:16 ` Eli Zaretskii
2024-05-28 18:45 ` Daniel Clemente
2024-05-28 19:17 ` Eli Zaretskii
2024-05-29 5:56 ` Daniel Clemente
2024-05-29 16:35 ` Eli Zaretskii
2024-05-30 9:55 ` Daniel Clemente
2024-05-30 12:05 ` Eli Zaretskii
2024-06-07 16:08 ` Daniel Clemente
2024-06-07 19:46 ` Eli Zaretskii
[not found] ` <CAJKAhPBdc2Og+UsgoCVwK_AOKnewdF5P3aV86Mr-FJOz4zNVvg@mail.gmail.com>
2024-06-10 16:30 ` Eli Zaretskii
2024-06-12 13:47 ` Daniel Clemente
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=CAJKAhPDv2AufASSYGr0usG5Ocs-FfKvwGmwKk4HKa_VBAhPxpQ@mail.gmail.com \
--to=n142857@gmail.com \
--cc=71224@debbugs.gnu.org \
--cc=eliz@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).