rizsotto.mailinglist added inline comments. ================ Comment at: tools/scan-build-py/libear/ear.c:142 @@ +141,3 @@ +#endif + if (!initialized) + initialized = bear_capture_env_t(&initial_env); ---------------- to run the full test set
> PATH=$(pwd)/bin:$PATH python -m unittest discover to run that specific test > PATH=$(pwd)/bin:$PATH python -m unittest -v > tests.functional.cases.test_create_cdb.CompilationDatabaseTest.test_successful_build_on_empty_env to more about run tests https://docs.python.org/2/library/unittest.html ================ Comment at: tools/scan-build-py/libear/ear.c:142 @@ +141,3 @@ +#endif + if (!initialized) + initialized = bear_capture_env_t(&initial_env); ---------------- rizsotto.mailinglist wrote: > to run the full test set > > > PATH=$(pwd)/bin:$PATH python -m unittest discover > > to run that specific test > > > PATH=$(pwd)/bin:$PATH python -m unittest -v > > tests.functional.cases.test_create_cdb.CompilationDatabaseTest.test_successful_build_on_empty_env > > to more about run tests > > https://docs.python.org/2/library/unittest.html my understanding on the `_NSGetEnviron` is, that it shall be used when the library is during the load process. later when the build process calls `execv` the load process is over, and `environ` variable is available. an earlier version of this code had a `get_environ` method, which were either return the `environ` variable or called the `_NSGetEnviron`. then i made this change and the tests were still passing, so i don't see where your issue is coming from. please tell me what kind of test you run against it to find it as problem. would like to add it to the test suite. http://reviews.llvm.org/D9600 _______________________________________________ cfe-commits mailing list cfe-commits@lists.llvm.org http://lists.llvm.org/cgi-bin/mailman/listinfo/cfe-commits
