From: Eli Zaretskii <eliz@gnu.org>
To: Evgeny Kurnevsky <kurnevsky@gmail.com>
Cc: 74922@debbugs.gnu.org
Subject: bug#74922: Fwd: bug#74922: 29.4; copy_string_contents doesn't always produce a valid utf-8
Date: Tue, 17 Dec 2024 17:10:36 +0200 [thread overview]
Message-ID: <86zfkumjkj.fsf@gnu.org> (raw)
In-Reply-To: <CAOEHfogetPusuLUajxMxuEyWs=yQuMoLo9wk+Xd7eFwJp_6-nA@mail.gmail.com> (message from Evgeny Kurnevsky on Tue, 17 Dec 2024 14:46:28 +0000)
> From: Evgeny Kurnevsky <kurnevsky@gmail.com>
> Date: Tue, 17 Dec 2024 14:46:28 +0000
> Cc: 74922@debbugs.gnu.org
>
> It can definitely do it, but I guess in emacs-module-rs it's not done by default because of performance
> implications - it might be quite costly to check every string in some cases, and it wasn't really clear if emacs
> can pass an invalid string. So currently this case causes undefined behavior there which results in emacs
> crash.
What do Rust programs do when they are told to read random files?
This is the same situation, basically.
And what would the module do if copy_string_contents *did* signal an
error?
prev parent reply other threads:[~2024-12-17 15:10 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-12-17 6:08 bug#74922: 29.4; copy_string_contents doesn't always produce a valid utf-8 Evgeny Kurnevsky
2024-12-17 13:18 ` Eli Zaretskii
[not found] ` <CAOEHfojGKXoUKbf1-5N=973OURs==BQTXejLFd8cLhsR1DWh+g@mail.gmail.com>
2024-12-17 13:31 ` bug#74922: Fwd: " Evgeny Kurnevsky
2024-12-17 14:24 ` Eli Zaretskii
2024-12-17 14:46 ` Evgeny Kurnevsky
2024-12-17 15:10 ` Eli Zaretskii [this message]
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=86zfkumjkj.fsf@gnu.org \
--to=eliz@gnu.org \
--cc=74922@debbugs.gnu.org \
--cc=kurnevsky@gmail.com \
/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).