From: "Óscar Fuentes" <ofv@wanadoo.es>
To: Cyril Arnould <cyril.arnould@outlook.com>
Cc: 73444@debbugs.gnu.org, Eli Zaretskii <eliz@gnu.org>
Subject: bug#73444: 30.0.50; mingw-w64: Emacs uses CRT's `read` when _FORTIFY_SOURCE > 0
Date: Wed, 25 Sep 2024 12:13:02 +0200 [thread overview]
Message-ID: <87v7ykvy6p.fsf@telefonica.net> (raw)
In-Reply-To: <PAWPR10MB776986E318800B89028B74F7F0682@PAWPR10MB7769.EURPRD10.PROD.OUTLOOK.COM> (Cyril Arnould's message of "Wed, 25 Sep 2024 00:25:23 +0200")
Cyril Arnould <cyril.arnould@outlook.com> writes:
> I've tested the workaround applied to master and AFAICT it fixes
> #63752. Emacs
> was pretty much unusable throughout in the bugged build, with the workaround
> it behaves normally.
Thanks for testing. I will apply the workaround with the adjustments
requested by Eli.
next parent reply other threads:[~2024-09-25 10:13 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <PAWPR10MB776986E318800B89028B74F7F0682@PAWPR10MB7769.EURPRD10.PROD.OUTLOOK.COM>
2024-09-25 10:13 ` Óscar Fuentes [this message]
2024-09-25 11:46 ` bug#73444: 30.0.50; mingw-w64: Emacs uses CRT's `read` when _FORTIFY_SOURCE > 0 Eli Zaretskii
2024-09-23 22:15 Óscar Fuentes
[not found] ` <handler.73444.B.17271297536353.ack@debbugs.gnu.org>
2024-09-23 22:29 ` Óscar Fuentes
2024-09-24 11:51 ` Eli Zaretskii
2024-09-24 12:34 ` Óscar Fuentes
2024-09-24 13:12 ` Eli Zaretskii
2024-09-24 14:06 ` Óscar Fuentes
2024-09-24 15:36 ` Eli Zaretskii
2024-09-24 11:48 ` Eli Zaretskii
2024-09-24 12:55 ` Óscar Fuentes
2024-09-24 13:27 ` Eli Zaretskii
2024-09-30 16:10 ` Óscar Fuentes
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=87v7ykvy6p.fsf@telefonica.net \
--to=ofv@wanadoo.es \
--cc=73444@debbugs.gnu.org \
--cc=cyril.arnould@outlook.com \
--cc=eliz@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 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).