GNU bug report logs - #74922
29.4; copy_string_contents doesn't always produce a valid utf-8

Previous Next

Full log

Message #20 received at 74922 <at> debbugs.gnu.org (full text, mbox):

From: Eli Zaretskii <eliz <at> gnu.org>
To: Evgeny Kurnevsky <kurnevsky <at> gmail.com>
Cc: 74922 <at> debbugs.gnu.org
Subject: Re: 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

> From: Evgeny Kurnevsky <kurnevsky <at> gmail.com>
> Date: Tue, 17 Dec 2024 14:46:28 +0000
> Cc: 74922 <at> 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?

Previous Next

GNU bug tracking system
Copyright (C) 1999 Darren O. Benham, 1997,2003 nCipher Corporation Ltd, 1994-97 Ian Jackson.