From: Eli Zaretskii <eliz@gnu.org>
To: andrei.elkin@pp.inet.fi
Cc: 48252@debbugs.gnu.org
Subject: bug#48252: Crashes continue ...
Date: Fri, 29 Oct 2021 18:55:58 +0300 [thread overview]
Message-ID: <83bl37rfjl.fsf@gnu.org> (raw)
In-Reply-To: <87bl37amy4.fsf@quad> (andrei.elkin@pp.inet.fi)
> From: andrei.elkin@pp.inet.fi
> Cc: 48252@debbugs.gnu.org
> Date: Fri, 29 Oct 2021 18:08:03 +0300
>
> Eli Zaretskii <eliz@gnu.org> writes:
>
> >> From: andrei.elkin@pp.inet.fi
> >> Date: Thu, 28 Oct 2021 16:38:00 +0300
> >>
> >> ...and what maybe is better that the most recent stack, below, is much shorter.
> >> And I am leaving it alive in case there will be interest or just further
> >> instruction for me.
> >
> > Please invoke xbacktrace and post the results. (If GDB says it
> > doesn't know that command, say "source /path/to/emacs/src/.gdbinit"
> > first.)
>
> (gdb) xbacktrace
> "command-error-default-function" (0xffffd448)
> "apply" (0xffffd618)
> 0xea3950a0 PVEC_COMPILED
Is that all? It should be a lot longer.
next prev parent reply other threads:[~2021-10-29 15:55 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 [this message]
[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
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=83bl37rfjl.fsf@gnu.org \
--to=eliz@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).