all messages for Emacs-related lists mirrored at yhetil.org
 help / color / mirror / code / Atom feed
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 16:31:16 +0300	[thread overview]
Message-ID: <83tu3sni6z.fsf@gnu.org> (raw)
In-Reply-To: <83wn8onk2d.fsf@gnu.org> (message from Eli Zaretskii on Tue, 25 Oct 2022 15:50:50 +0300)

> Cc: luangruo@yahoo.com, 58767@debbugs.gnu.org
> Date: Tue, 25 Oct 2022 15:50:50 +0300
> From: Eli Zaretskii <eliz@gnu.org>
> 
> > Date: Tue, 25 Oct 2022 14:10:12 +0200 (CEST)
> > From: purity.piped@tuta.io
> > Cc: Po Lu <luangruo@yahoo.com>, 58767@debbugs.gnu.org
> > 
> > What I do that makes emacs crash is just launch telega. Either via a keybind or m-x. 
> 
> So just "M-x telega RET" is enough to cause the crash?

FTR: I tried to reproduce the crash, but couldn't get far enough:
running "M-x telega" requires some server, which I don't have, and
won't install.  So someone who has that installed will need to debug
this and tell me how come this code crashes.

The abort is in this code in bidi.c:

  /* Don't move at end of buffer/string.  */
  else if (bidi_it->charpos < (string_p ? bidi_it->string.schars : ZV))
    {
      /* Advance to the next character, skipping characters covered by
	 display strings (nchars > 1).  */
      if (bidi_it->nchars <= 0)
	emacs_abort ();
      bidi_it->charpos += bidi_it->nchars;
      if (bidi_it->ch_len == 0)
	emacs_abort ();
      bidi_it->bytepos += bidi_it->ch_len;
      prev_type = bidi_it->orig_type;
    }

The backtrace points to the first call to emacs_abort, but since this
is an optimized build, it could be the second one as well.  These
situations "should not happen", ever.  So I must understand what kind
of buffer or string text we bumped into that caused this, it should be
something highly unusual.





  reply	other threads:[~2022-10-25 13:31 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 [this message]
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
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=83tu3sni6z.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.