From: Eli Zaretskii <eliz@gnu.org>
To: Evgeny Kurnevsky <kurnevsky@gmail.com>
Cc: 74922@debbugs.gnu.org
Subject: bug#74922: 29.4; copy_string_contents doesn't always produce a valid utf-8
Date: Tue, 17 Dec 2024 15:18:07 +0200 [thread overview]
Message-ID: <86msguo3cg.fsf@gnu.org> (raw)
In-Reply-To: <CAOEHfoie90-DbZ=uLBJAKgKPGc2+iqi7Ggh3Y5p9RY80yi_CrQ@mail.gmail.com> (message from Evgeny Kurnevsky on Tue, 17 Dec 2024 06:08:30 +0000)
> From: Evgeny Kurnevsky <kurnevsky@gmail.com>
> Date: Tue, 17 Dec 2024 06:08:30 +0000
>
> According to the docs and comment inside module_copy_string_contents it should always produce a valid
> utf-8 string that can be used in dynamic modules, but it seems it's not always the case. I encountered an
> emacs crash when using emacs-module-rs because it always expects a valid utf-8 for strings. To reproduce
> you can call:
>
> (some-function-from-dynamic-library (encode-coding-string (f-read-text "wg-private-pc.age") 'utf-8 t))
>
> The file is
> https://github.com/kurnevsky/nixfiles/raw/0b3de016dac551398627a55788b80d4809afcbf9/secrets/wg-private-pc.age
This string includes raw bytes, it isn't a text string, as far as I
could see. It definitely isn't UTF-8 encoded text. What did you
expect to happen with it when you copy such a string from Emacs?
> See https://github.com/ubolonton/emacs-module-rs/issues/58 for additional details.
Can't say there are too many details there...
next prev parent reply other threads:[~2024-12-17 13:18 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 [this message]
[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
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=86msguo3cg.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).