[clang-tidy] CloexecDupCheck: Always pass the third argument

[sgallagher]

Summary

When running valgrind, the third argument is read implicitly from
the stack, resulting in an EINVAL return from the fcntl(). We should
explicitly be setting the third argument to zero to ensure that we
don't break valgrind.

Signed-off-by: Stephen Gallagher <[e-mail]>

clang-tools-extra/clang-tidy/android/CloexecDupCheck.cpp

 
 void CloexecDupCheck::check(const MatchFinder::MatchResult &Result) {
   std::string ReplacementText =
-      (Twine("fcntl(") + getSpellingArg(Result, 0) + ", F_DUPFD_CLOEXEC)")
+      (Twine("fcntl(") + getSpellingArg(Result, 0) + ", F_DUPFD_CLOEXEC, 0)")
           .str();
 
   replaceFunc(Result,