On Jul 22 07:44, Radek Barton via Cygwin-patches wrote: > Hello. > > I understand your concern and thank you for brining it in. If I > understand the comment at > https://github.com/Windows-on-ARM-Experiments/newlib-cygwin/blob/woarm64/winsup/cygwin/lib/_cygwin_crt0_common.cc#L123 > correctly, this can happen when Cygwin application is linked with > non-Cygwin stdlib. I don't know if this is a legit use-case supported > on x64
Uh, yes and no. You don't need to link against another stdlib, you just have to provide your own malloc/free. And it's a valid use-case on x64 as well. Consider tcsh, which comes with its own malloc/free routines. Or helper libs like dmalloc. Corinna
