libs/newlib-cygwin
libs
/
newlib-cygwin
mirror of git://sourceware.org/git/newlib-cygwin.git
4
0
Fork 0
Code Issues Projects Releases Wiki Activity
newlib-cygwin/winsup/cygwin/release/3.4.10

15 lines
549 B
Plaintext
Raw Normal View History

Cygwin: Add relnote to 3.4.10 release file Document the most recent update to include/sys/cpuset.h.
2023-09-09 14:48:30 +08:00
Bug Fixes
---------
- Fix missing term in __cpuset_zero_s() prototoype in sys/cpuset.h.
Addresses: https://cygwin.com/pipermail/cygwin/2023-September/254423.html
Cygwin: cwd: avoid releasing the cwdstuff SRW Lock twice cwdstuff::set has a code snippet handling the case where a process can't create a handle to a directory, e. g., due to permissions. Commit 88443b0a22589 ("cwdstuff: Don't leave from setting the CWD prematurely on init") introduced a special case to handle this situation at process initialization. It also introduces an early mutex release, which is not required, but ok, because we're in the init phase. Releasing the mutex twice is no problem since the mutexes are recursive. Fast forward to commit 0819679a7a210 ("Cygwin: cwd: use SRWLOCK instead of muto"). The mechanical change from a recursive mutex to a non-recursive SRWLOCK failed to notice that this very specific situation will release the SRWLOCK twice. Remove the superfluous release action. While at it, don't set dir to NULL, but h, since dir will get the value of h anyway later on. Setting h to NULL may not be necessary, but better safe than sorry. Reported-by: tryandbuy >tryandbuy@proton.me> Fixes: 88443b0a22589 ("cwdstuff: Don't leave from setting the CWD prematurely on init") Fixes: 0819679a7a210 ("Cygwin: cwd: use SRWLOCK instead of muto") Signed-off-by: Corinna Vinschen <corinna@vinschen.de>
2023-10-31 02:40:31 +08:00
- Fix hang in process initialization if cwd is unreadable.
Addresses: https://cygwin.com/pipermail/cygwin/2023-October/254604.html
Cygwin: let feraiseexcept actually raise an exception The exception handling inside of Cygwin functions marked as SIGFE covers exceptions and lets the library code handle them gracefully. If these functions want to raise an exception, they have to send a signal explicitely via raise(3). That's not what we want in feraiseexcept(). It triggers a floating point exception explicitely by calling the i387 op "fwait". Being marked as SIGFE, this exception will be suppressed and the normal exception handling won't kick in. Fix this by moving feraiseexcept into the NOSIGFE realm. Fixes: 0f81b5d4bcaa ("* Makefile.in (DLL_OFILES): Add new fenv.o module.") Signed-off-by: Corinna Vinschen <corinna@vinschen.de>
2023-10-31 20:07:36 +08:00
- Let feraiseexcept actually raise an exception.
Addresses: https://cygwin.com/pipermail/cygwin/2023-October/254667.html
Add release text for random(3) fix Signed-off-by: Corinna Vinschen <corinna@vinschen.de>
2023-11-14 03:01:36 +08:00
- Make random(3) family of functions thread-safe.
Addresses: https://cygwin.com/pipermail/cygwin/2023-November/254734.html