News for hackers. Stuff that matters.

A comment on Don't setenv in multi-threaded code on glibc. Parent comment

Re:Don't setenv in multi-threaded code on glibc by quotemstr on Tuesday January 31, 2017 @01:11PM (#13533392)
Upthread, I pointed out a sane and safe alternative to POSIX getenv interface, one that works fine with regular C, and here, you're claiming that we need exotic features to achieve safety? What?
[ Parent | on HN ]
Re:Don't setenv in multi-threaded code on glibc by pjmlp on Tuesday January 31, 2017 @03:08PM (#13534712)
Because you only focused on getenv.

I was replying about the whole UNIX API surface, regarding functions like strcpy.

You need exotic features to guarantee that the memory doesn't get corrupted.

[ Parent | on HN ]