Permalink
Comparing changes
Choose two branches to see what’s changed or to start a new pull request.
If you need to, you can also or
learn more about diff comparisons.
Open a pull request
Create a new pull request by comparing changes across two branches. If you need to, you can also .
Learn more about diff comparisons here.
...
Able to merge.
These branches can be automatically merged.
52
contributors
Commits on Nov 5, 2016
Commits on Jun 19, 2017
-
Allow death test child to bypass WER under MinGW
The mechanics of suppressing debugger trapping and Windows Error Reporting for the crashed child process in a death test are currently guarded under the `GTEST_HAS_SEH` macro. This seems unnecessary, as the logic does not call any APIs related to Structured Error Handling. Replace the guarding macro with the more permissive `GTEST_OS_WINDOWS`, so that Windows toolchains without SEH support (e.g. MinGW) can benefit from it. Fixes: google#1116
Commits on Jun 30, 2017
-
*Silence false positive memory leaks reported by Microsoft's debug CRT*
Add a new RAII MemoryIsNotDeallocated class that excludes memory allocations from Microsoft’s debug CRT leak detection report. We use this RAII class to silence 2 false positive leaks that are caused by memory allocations that are intentionally never deallocated. *Background* The MS debug CRT has a lightweight memory leak detection mechanism that can only detect if a memory allocation is missing a matching deallocation. Consequently, it will report a false positive leak for memory that’s intentionally never deallocated. For example, memory that’s reachable for the entire lifetime of a app. Note the MS debug CRT is always tracking memory allocations but the final memory leak report is disabled by default. As you can’t avoid paying for its cost, you may as well use it. The memory leak report can be enabled by calling the following function #ifdef _MSC_VER _CrtSetDbgFlag(_CrtSetDbgFlag(_CRTDBG_REPORT_FLAG) | _CRTDBG_LEAK_CHECK_DF); #endif // _MSC_VER anywhere before exiting main. For example, the following are the false positive leaks reported before this change; Detected memory leaks! Dumping objects -> {750} normal block at 0x015DF938, 8 bytes long. Data: < ] > 00 F9 5D 01 00 00 00 00 {749} normal block at 0x015DEE60, 32 bytes long. Data: <` ] ` ] ` ] > 60 EE 5D 01 60 EE 5D 01 60 EE 5D 01 01 01 CD CD {748} normal block at 0x015DF900, 12 bytes long. Data: <8 ] ` ] > 38 F9 5D 01 60 EE 5D 01 00 00 00 00 {747} normal block at 0x015DA0F8, 24 bytes long. Data: < > FF FF FF FF FF FF FF FF 00 00 00 00 00 00 00 00 Object dump complete. As you can see from above it’s not easy to identify the above are false positives. Consequently, if false positive leaks are not fixed or silenced, then it becomes impractical to identify real memory leaks.
Commits on Aug 10, 2017
Commits on Aug 16, 2017
Commits on Aug 21, 2017
Commits on Sep 6, 2017
Commits on Nov 19, 2017
Commits on Nov 24, 2017
Commits on Dec 7, 2017
Commits on Dec 8, 2017
Commits on Dec 12, 2017
Commits on Dec 31, 2017
Commits on Jan 12, 2018
Commits on Feb 12, 2018
Commits on Mar 5, 2018
-
Merge branch 'fix_death_test_child_mingw_wer_issue1116' of https://gi…
…thub.com/tanzislam/googletest into fix_death_test_child_mingw_wer_issue1116
Commits on Mar 12, 2018
-
Merge pull request google#1502 from gennadiycivil/master
merges-port(1)
-
Allow macros inside of parametrized test names.
This allows doing things like TEST_P(TestFixture, MAYBE(TestName)) for nicer conditional test disabling. Upstream of cr/188748737. Tested: Added unit tests MacroNamingTest and MacroNamingTestNonParametrized.
-
-
Merge pull request google#1503 from sheepmaster/upstream_188748737
Allow macros inside of parametrized test names.
Commits on Mar 13, 2018
Commits on Mar 14, 2018
Commits on Mar 15, 2018
Commits on Mar 16, 2018
Commits on Mar 19, 2018
-
Merge pull request google#1508 from gennadiycivil/master
merge, again, IsRecursiveContainer
There are no files selected for viewing
This file was deleted.