On Thu, 3 Jul 2025, Igor Kostenko wrote:
Hi LIU Hao,
I've borrowed the term 'canary' from the few documentation bits.
https://www.redhat.com/en/blog/security-technologies-stack-smashing-protection-stackguard
https://lwn.net/Articles/584225/
https://wiki.osdev.org/Stack_Smashing_Protector
But I u
Hi LIU Hao,
I've borrowed the term 'canary' from the few documentation bits.
https://www.redhat.com/en/blog/security-technologies-stack-smashing-protection-stackguard
https://lwn.net/Articles/584225/
https://wiki.osdev.org/Stack_Smashing_Protector
But I used it too loosely.
The updated patch is be
在 2025-7-3 20:06, Igor Kostenko 写道:
Fix stack protection bootstrapping issue where the canary initialization
function itself triggers false positive stack overflow detection.
Signed-off-by: Igor Kostenko
---
mingw-w64-crt/ssp/stack_chk_guard.c | 6 +-
1 file changed, 5 insertions(+), 1 d
```
This is not specific to UCRT. It looks like legacy CRT behavior; all MSVCR*
DLLs are also affected.
```
Yes, this issue seems to come from old CRTs. My wording probably wasn't clear,
UCRT-specific part was that return value is correct with UTF-8 locales.
```
I have no idea about how widely
在 2025-7-3 00:04, Kirill Makurin 写道:
More information about this issue for anyone who's interested.
It seems that return value of mbrtowc is broken only with DBCS code pages. The
return value is correct when using UCRT's mbrtowc with UTF-8 locales.
The issue with mbrtowc has direct effect on m
On Wed, Jul 2, 2025 at 4:00 PM Biswapriyo Nath wrote:
> > I know from recent reading that the MSYS2 project is trying to become
> more
> > aligned with the Cygwn distribution, so the triplet is now moving towards
> > x86_64-pc-cygwin.
>
> That change should not affect MINGW-packages. If the quest
