@fleckenstein @navi Here it seems to be mostly reproducible at least.

By the way here's what I got from it:
- Claims fd leak with dup2, I guess expecting me to close fildes2 while dup2 *expects* to be the one closing fildes2 as it returns -1 if it fails to close or if it isn't valid
- Claims a leak of FILE, that one I could see why it happens… (list of arguments to open them, same list of arguments to close them, instead of say looping on the array of opened files, which hopefully it would then analyze correctly)
- (non-reproducible) Claims an invalid fd getting passed, even though it's when open returns 'fd > 0' which by definition is valid (negative fd being invalid)

And no other claims so all were invalid. (That said, I fixed everything but dead increments from llvm/clang static analyzer).