all messages for Emacs-related lists mirrored at yhetil.org
 help / color / mirror / code / Atom feed
From: Po Lu <luangruo@yahoo.com>
To: Eli Zaretskii <eliz@gnu.org>
Cc: emacs-devel@gnu.org
Subject: Re: master 6ed1994d27: Prevent crashes from illegal locale coding systems
Date: Tue, 15 Feb 2022 21:55:54 +0800	[thread overview]
Message-ID: <87czjow7x1.fsf@yahoo.com> (raw)
In-Reply-To: <837d9w450e.fsf@gnu.org> (Eli Zaretskii's message of "Tue, 15 Feb 2022 15:46:09 +0200")

Eli Zaretskii <eliz@gnu.org> writes:

> [Why private email?]

Sorry for that, I copied in the list again.  And I apologize for sending
all of this twice.

> But this means we cannot call the decoding stuff there at all, because
> some coding-systems call into Lisp, and Lisp can signal an error.  So
> we probably should take the raw bytes in that place, record them in
> the event queue, and then decode it later, when it's safe.

What safe place would you find appropriate for the job?  And I'm not
sure if we have a mechanism in place to record the raw bytes that way,
so one will have to be devised.

> Are there other situations where we decode stuff inside
> handle_one_xevent or in a XIM callback?

There aren't any, AFAICT, other than the ones that I changed.

> If so, and if what you write is really accurate, then we have a
> ticking bomb waiting to go off, and we should defuse it ASAP.

Indeed.

> But given what you say above I think we have a much more serious
> problem on our hands.

Based on what you have said, I agree.

Thanks in advance.



  parent reply	other threads:[~2022-02-15 13:55 UTC|newest]

Thread overview: 24+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-02-13 13:00 master 6ed1994d27: Prevent crashes from illegal locale coding systems Eli Zaretskii
2022-02-13 13:16 ` Po Lu
2022-02-13 13:45   ` Eli Zaretskii
2022-02-14  0:51     ` Po Lu
2022-02-14  3:32       ` Eli Zaretskii
2022-02-14  4:46         ` Po Lu
2022-02-14 14:07           ` Eli Zaretskii
     [not found]             ` <87iltheyeu.fsf@yahoo.com>
     [not found]               ` <83wnhwol2o.fsf@gnu.org>
     [not found]                 ` <87tud0ybhj.fsf@yahoo.com>
     [not found]                   ` <837d9w450e.fsf@gnu.org>
2022-02-15 13:55                     ` Po Lu [this message]
2022-02-15 14:07                       ` Eli Zaretskii
2022-02-16  0:49                         ` Po Lu
2022-02-16  2:38                           ` Po Lu
2022-02-16  5:12                             ` Po Lu
2022-02-16 12:22                               ` Eli Zaretskii
2022-02-16 12:33                                 ` Po Lu
2022-02-16 12:38                                   ` Eli Zaretskii
2022-02-16 13:05                                     ` Po Lu
2022-02-16 13:33                                       ` Eli Zaretskii
2022-02-16 13:40                                         ` Po Lu
2022-02-16 14:05                                           ` Eli Zaretskii
2022-02-17  0:45                                             ` Po Lu
2022-02-17  6:31                                               ` Eli Zaretskii
2022-02-17  6:51                                                 ` Po Lu
2022-02-17  7:23                                                   ` Eli Zaretskii
2022-02-17  7:44                                                     ` Po Lu

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=87czjow7x1.fsf@yahoo.com \
    --to=luangruo@yahoo.com \
    --cc=eliz@gnu.org \
    --cc=emacs-devel@gnu.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 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.