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 @11:53PM (#13538367)
So what? Under that scheme, you can take the locks, but the lock-protected data structures are probably garbage. (That is, the locks become implicitly "abandoned", not "unlocked".)
[ Parent | on HN ]
Re:Don't setenv in multi-threaded code on glibc by loeg on Wednesday February 01, 2017 @08:18PM (#13547206)
I'm not defending it as a model. I think python's approach to fork & thread interaction, which is to punt on it completely while exposing both to end users, is pretty broken.
[ Parent | on HN ]