From: Eli Zaretskii <eliz@gnu.org>
To: purity.piped@tuta.io
Cc: luangruo@yahoo.com, 58767@debbugs.gnu.org
Subject: bug#58767: telega makes emacs crash (under an EXWM session?)
Date: Tue, 25 Oct 2022 21:03:40 +0300 [thread overview]
Message-ID: <83o7tzok5f.fsf@gnu.org> (raw)
In-Reply-To: <NFFCO-Y--3-9@tuta.io> (purity.piped@tuta.io)
> Date: Tue, 25 Oct 2022 19:36:32 +0200 (CEST)
> From: purity.piped@tuta.io
> Cc: luangruo@yahoo.com, 58767@debbugs.gnu.org
>
> I've tested telega with emacs-29 (I cloned from savannah.gnu.org), and it appears that, indeed, telega does
> not seem to crash there.
Thanks. If Emacs 29 doesn't crash, then I guess the issue, whatever
it is, was already fixed.
> Thread 1 "emacs" received signal SIGABRT, Aborted.
> 0x00007ffff596c64c in ?? () from /usr/lib/libc.so.6
> (gdb) bt
> #0 0x00007ffff596c64c in () at /usr/lib/libc.so.6
> #1 0x00007ffff591c958 in raise () at /usr/lib/libc.so.6
> #2 0x0000555555700a40 in terminate_due_to_signal (sig=6, backtrace_limit=40) at emacs.c:437
> #3 0x000055555572e7a9 in emacs_abort () at sysdep.c:2282
> #4 0x00005555556900bf in bidi_resolve_explicit (bidi_it=0x7fffffff8760) at bidi.c:1949
This is indeed the second emacs_abort, not the one shown by GDB in the
optimized build.
next prev parent reply other threads:[~2022-10-25 18:03 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-10-24 17:07 bug#58767: telega makes emacs crash (under an EXWM session?) Marco via Bug reports for GNU Emacs, the Swiss army knife of text editors
2022-10-25 0:36 ` Po Lu via Bug reports for GNU Emacs, the Swiss army knife of text editors
[not found] ` <NFCUgqi--3-9@tuta.io>
[not found] ` <87tu3s2vtn.fsf@yahoo.com>
[not found] ` <NFD5mZ9--3-9@tuta.io>
[not found] ` <87lep42unz.fsf@yahoo.com>
[not found] ` <NFDFQyP--3-9@tuta.io>
2022-10-25 9:58 ` Po Lu via Bug reports for GNU Emacs, the Swiss army knife of text editors
2022-10-25 11:35 ` Eli Zaretskii
2022-10-25 12:10 ` purity.piped--- via Bug reports for GNU Emacs, the Swiss army knife of text editors
2022-10-25 12:50 ` Eli Zaretskii
2022-10-25 13:31 ` Eli Zaretskii
2022-10-25 17:36 ` purity.piped--- via Bug reports for GNU Emacs, the Swiss army knife of text editors
2022-10-25 18:03 ` Eli Zaretskii [this message]
2022-10-25 18:25 ` Stefan Kangas
2022-10-27 10:05 ` purity.piped--- via Bug reports for GNU Emacs, the Swiss army knife of text editors
2022-10-27 13:22 ` Eli Zaretskii
2022-10-27 13:33 ` purity.piped--- via Bug reports for GNU Emacs, the Swiss army knife of text editors
2022-10-27 15:49 ` Eli Zaretskii
2022-10-28 0:47 ` Po Lu via Bug reports for GNU Emacs, the Swiss army knife of text editors
2022-10-28 8:21 ` purity.piped--- via Bug reports for GNU Emacs, the Swiss army knife of text editors
2022-10-27 13:35 ` Po Lu via Bug reports for GNU Emacs, the Swiss army knife of text editors
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
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=83o7tzok5f.fsf@gnu.org \
--to=eliz@gnu.org \
--cc=58767@debbugs.gnu.org \
--cc=luangruo@yahoo.com \
--cc=purity.piped@tuta.io \
/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 external index
https://git.savannah.gnu.org/cgit/emacs.git
https://git.savannah.gnu.org/cgit/emacs/org-mode.git
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.