From: Stefan Kangas <stefankangas@gmail.com>
To: bertieb <emacs@bertieb.org>
Cc: eliz <eliz@gnu.org>, 62002 <62002@debbugs.gnu.org>
Subject: bug#62002: 28.2; 28.2; intermittent crash on scroll (arch + spacemacs)
Date: Wed, 10 Jan 2024 02:46:36 -0800 [thread overview]
Message-ID: <CADwFkmnSQ2-vGe9=TtE2TzrF0Hy7DQrFYyNvE-m7Vd6QTkr6TA@mail.gmail.com> (raw)
In-Reply-To: <CADwFkmkQZndZE773KxMYDS=zOd1UQ0YtQ5nUoPT6ETvs0F8K6w@mail.gmail.com> (Stefan Kangas's message of "Tue, 12 Sep 2023 14:19:31 -0700")
Stefan Kangas <stefankangas@gmail.com> writes:
> bertieb <emacs@bertieb.org> writes:
>
>> I see it very infrequently, though I recently had an extended bout of uptime and so wasn't re-launching emacs.
>>
>> coredumpctl bears this out:
>>
>> TIME PID UID GID SIG COREFILE EXE SIZE
>> Sun 2023-05-07 10:32:03 BST 2167614 1000 1000 SIGSEGV missing /usr/bin/emacs-28.2 -
>> Tue 2023-06-20 13:04:39 BST 369029 1000 1000 SIGSEGV missing /usr/bin/emacs-28.2 -
>> Thu 2023-07-20 11:58:06 BST 3750394 1000 1000 SIGSEGV missing /usr/bin/emacs-28.2 -
>> Fri 2023-08-11 12:35:44 BST 964942 1000 1000 SIGABRT missing /usr/bin/emacs-29.1 -
>>
>> Judging by the frequency I am about due another crash!
>
> Can you try catching it under gdb and with debug symbols?
That was four months ago. Any luck with reproducing it?
Also, can you reproduce it using 29.1 or 29.1.90?
next prev parent reply other threads:[~2024-01-10 10:46 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-03-06 12:16 bug#62002: 28.2; 28.2; intermittent crash on scroll (arch + spacemacs) emacs
2023-03-06 16:44 ` Eli Zaretskii
2023-03-06 20:14 ` bug#62002: " emacs
2023-09-12 0:51 ` bug#62002: 28.2; " Stefan Kangas
2023-09-12 21:03 ` bertieb
2023-09-12 21:19 ` Stefan Kangas
2024-01-10 10:46 ` Stefan Kangas [this message]
[not found] ` <18cf3307166.ea9f3076799496.5108076072539468390@bertieb.org>
2024-01-10 11:57 ` Stefan Kangas
2024-01-10 11:57 ` bertieb
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='CADwFkmnSQ2-vGe9=TtE2TzrF0Hy7DQrFYyNvE-m7Vd6QTkr6TA@mail.gmail.com' \
--to=stefankangas@gmail.com \
--cc=62002@debbugs.gnu.org \
--cc=eliz@gnu.org \
--cc=emacs@bertieb.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).