From: andrei.elkin--- via "Bug reports for GNU Emacs, the Swiss army knife of text editors" <bug-gnu-emacs@gnu.org>
To: 48252@debbugs.gnu.org
Subject: bug#48252: Crashes continue ...
Date: Wed, 21 Dec 2022 15:18:39 +0200 [thread overview]
Message-ID: <87y1r0evyo.fsf@quad> (raw)
In-Reply-To: <83r1ikdxly.fsf@gnu.org>
Hello again!
I have a question below.
Meanwhile ...
the stack persistently comes back for me, and yesterday in the
up-to-date emacs-28 branch (version 28.2.50).
It takes some days, maybe weeks until I start feeling some slowness
in responses to commands.
I must have learned that the stack appears in correlation with
C-k or just delete-char commands.
I previously thought it might have something to do with `lsp`. Can't yet
dismiss that feeling.
What if I skip (comment out)
#1 print_object
if I know somehow that SYMBOL_NAME() will segfault?
If that would deter emacs from crashing even for few more weeks :-), I'd
be happier than I am now.
Cheers,
Andrei
next prev parent reply other threads:[~2022-12-21 13:18 UTC|newest]
Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <87pmyeekkq.fsf@quad>
[not found] ` <837dkmhavj.fsf@gnu.org>
[not found] ` <87wnsma5aw.fsf@quad>
[not found] ` <83im46fq68.fsf@gnu.org>
[not found] ` <87y2cupcb6.fsf@quad>
[not found] ` <837dke49jq.fsf@gnu.org>
[not found] ` <87wnsdob3m.fsf@quad>
[not found] ` <83o8dp2wba.fsf@gnu.org>
[not found] ` <871ralmhw2.fsf@quad>
2021-05-06 9:23 ` bug#48252: 28.0.50; Emacs crashes while printing an error message Eli Zaretskii
2021-05-06 15:01 ` andrei.elkin
2021-10-28 13:38 ` bug#48252: Crashes continue andrei.elkin
2021-10-28 15:53 ` Eli Zaretskii
2021-10-29 15:08 ` andrei.elkin
2021-10-29 15:55 ` Eli Zaretskii
[not found] ` <87cznn7npv.fsf@quad>
2021-10-29 19:25 ` Eli Zaretskii
2021-10-29 19:31 ` Eli Zaretskii
2021-10-30 11:07 ` andrei.elkin
2021-10-30 12:04 ` Eli Zaretskii
2022-06-02 13:19 ` bug#48252: 28.0.50; Emacs crashes while printing an error message Lars Ingebrigtsen
2022-07-01 11:03 ` Lars Ingebrigtsen
2022-11-22 18:14 ` bug#48252: Crashes continue andrei.elkin--- via Bug reports for GNU Emacs, the Swiss army knife of text editors
2022-12-21 13:18 ` andrei.elkin--- via Bug reports for GNU Emacs, the Swiss army knife of text editors [this message]
2022-12-21 13:56 ` Eli Zaretskii
2022-12-21 15:14 ` andrei.elkin--- via Bug reports for GNU Emacs, the Swiss army knife of text editors
2023-02-02 12:17 ` bug#48252: Possible Emacs 29 version of bug=48252 andrei.elkin--- via Bug reports for GNU Emacs, the Swiss army knife of text editors
2023-02-02 14:25 ` Eli Zaretskii
2023-02-02 13:38 ` bug#48252: Follow-up: " andrei.elkin--- via Bug reports for GNU Emacs, the Swiss army knife of text editors
2023-02-02 14:29 ` 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=87y1r0evyo.fsf@quad \
--to=bug-gnu-emacs@gnu.org \
--cc=48252@debbugs.gnu.org \
--cc=andrei.elkin@pp.inet.fi \
/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).