From cc660bd265172ffd75851d418db9af66704d0e54 Mon Sep 17 00:00:00 2001 From: Eli Zaretskii Date: Sat, 1 Jul 2023 10:01:59 +0300 Subject: [PATCH] ; * etc/PROBLEMS: Mention MinGW problems with -D_FORTIFY_SOURCE=2. --- etc/PROBLEMS | 15 +++++++++++++++ 1 file changed, 15 insertions(+) diff --git a/etc/PROBLEMS b/etc/PROBLEMS index cdce8bbc774..30769e68f11 100644 --- a/etc/PROBLEMS +++ b/etc/PROBLEMS @@ -2768,6 +2768,21 @@ With any of the above methods, you'd need to restart Emacs (and preferably also your Windows system) after making the changes, to have them take effect. +*** MinGW64 Emacs built with -D_FORTIFY_SOURCE=2 misbehaves + +Using this preprocessor option when building Emacs with MinGW64 +produces an Emacs binary that behaves incorrectly. In particular, +running asynchronous shell command, e.g., with 'M-&', causes Emacs to +use 100% of CPU and start allocating a lot of memory. For the same +reason, asynchronous native-compilation will hang Emacs (which could +wedge Emacs during startup, if your Emacs is configured to download +and install packages via package.el every startup). 'M-x run-python', +'M-x shell', and similar commands also hang. Other commands might +also cause high CPU and/or memory usage. + +The workaround is to rebuild Emacs without the -D_FORTIFY_SOURCE=2 +option. + ** Emacs on Windows 9X requires UNICOWS.DLL If that DLL is not available, Emacs will display an error dialog -- 2.39.2