summaryrefslogtreecommitdiffstats
path: root/googletest/src/gtest-death-test.cc
Commit message (Collapse)AuthorAgeFilesLines
* Merge pull request #4477 from tmiguelf:feature/soup_cleanupCopybara-Service2024-02-281-10/+10
|\ | | | | | | | | PiperOrigin-RevId: 611133343 Change-Id: Ieef806f51fcbc2877805dae415f76d03547b8dfa
| * Fixed gcc linker error 58refs/pull/4477/headTiago Freire2024-02-231-10/+20
|/
* Use _Exit instead of _exit in GoogleTestAbseil Team2024-02-071-6/+8
| | | | | | | | _Exit is standardized since C99, whereas _exit is POSIX-only. Fixes: #4447 PiperOrigin-RevId: 605000352 Change-Id: Ibfa84edaa043bd003a21383e8148bf45be7217f6
* changed http to httpsrefs/pull/4349/headsthd2023-08-221-1/+1
|
* Allow clients to un-suppress output from gUnit EXPECT_EXIT tests.Abseil Team2023-06-151-1/+1
| | | | | | | | This is useful for running individual tests in a separate process, which is useful for testing e.g. flag changes which have a process-global effect. PiperOrigin-RevId: 540580573 Change-Id: I18a5d24d79425a9d595be3369efc44e2f655f6f8
* Give CreateArgvFromArgs internal linkageAbseil Team2023-05-111-1/+4
| | | | | | | It isn't declared in any header or referenced from any other file. PiperOrigin-RevId: 531209642 Change-Id: I9e7df37f737b00994f8845ed38c3b775879cb25c
* Fix spellingrefs/pull/4227/headVertexwahn2023-04-251-1/+1
|
* Add missing std includesTom Hughes2023-04-201-0/+2
| | | | | PiperOrigin-RevId: 525850646 Change-Id: I64387f5b933beb79cd05636dca81b7a75213383e
* Internal Code ChangeAbseil Team2023-03-231-1/+1
| | | | | PiperOrigin-RevId: 518810140 Change-Id: Id3f9471f827894761080bc9199b0a092dc829b5f
* Fix minor bug -- if ExecDeathTestChildMain() ever returns, we should exitAbseil Team2023-03-211-2/+1
| | | | | | | with a non-zero status. PiperOrigin-RevId: 518306642 Change-Id: I72fb2764e477acb0362593c63f7748c4f64db0c6
* Add a comment to clarify Fuchsia process launcher requirement.Abseil Team2023-03-081-0/+5
| | | | | PiperOrigin-RevId: 515154129 Change-Id: I3dd9e912e160d09d1f74a467336212701d4e1b7d
* Use "#ifdef" with public macrosTom Hughes2023-03-061-2/+2
| | | | | | | This allows compilation with "-Wundef" (#3267). PiperOrigin-RevId: 513944726 Change-Id: I1a3854bb2333d5dec6c0ff91ee1eddd9a766ab91
* Use "#ifdef GTEST_OS_..." instead of "#if GTEST_OS_..."Tom Hughes2023-03-061-23/+23
| | | | | | | This is compatible with compiling with "-Wundef" (#3267). PiperOrigin-RevId: 513943378 Change-Id: I47cf5fabbb77be061c4483a0adc54511af6b191c
* Remove strdup usageAbseil Team2023-02-151-69/+25
| | | | | PiperOrigin-RevId: 509947007 Change-Id: I31e1274afa889776829c877c40c9af589298dcf2
* Merge pull request #3918 from assafpr:master2mainCopybara-Service2022-08-011-1/+1
|\ | | | | | | | | PiperOrigin-RevId: 464586117 Change-Id: Icda62f13b962f7408bb5698ae2b627391257d152
| * Update gtest-death-test.ccassafpr2022-06-271-1/+1
| |
* | gtest-death-test: add 'noreturn'refs/pull/3951/headMatei Dibu2022-07-201-1/+1
|/
* Running clang-format over all of GoogleTestAbseil Team2022-03-151-230/+203
| | | | | | | | | | | | | | | | A few tests are examining code locations and looking af the resulting line numbers to verify that GoogleTest shows those to users correctly. Some of those locations change when clang-format is run. For those locations, I've wrapped portions in: // clang-format off ... // clang-format on There may be other locations that are currently not tickled by running clang-format. PiperOrigin-RevId: 434844712 Change-Id: I3a9f0a6f39eff741c576b6de389bef9b1d11139d
* fix: typo codespelling commentrefs/pull/3499/headslowy072021-07-241-2/+2
|
* Googletest exportAbseil Team2021-07-071-40/+43
| | | | | | Introduce GTEST_FLAG_GET and GTEST_FLAG_SET macros. PiperOrigin-RevId: 382808313
* Googletest exportAbseil Team2021-05-131-3/+3
| | | | | | This callsite was previously updated to use ZX_INFO_PROCESS_V2 as a part of a soft transition. It is now time to revert back to `ZX_INFO_PROCESS` (which is now an alias of the former). See fxbug.dev/30751 for more details. PiperOrigin-RevId: 372339833
* Googletest exportAbseil Team2021-04-211-3/+3
| | | | | | This callsite was previously updated to use ZX_INFO_PROCESS_V2 as a part of a soft transition. It is now time to revert back to `ZX_INFO_PROCESS` (which is now an alias of the former). See fxbug.dev/30751 for more details. PiperOrigin-RevId: 369370855
* Googletest exportAbseil Team2021-04-211-3/+3
| | | | | | This callsite was previously updated to use ZX_INFO_PROCESS_V2 as a part of a soft transition. It is now time to revert back to `ZX_INFO_PROCESS` (which is now an alias of the former). See fxbug.dev/30751 for more details. PiperOrigin-RevId: 369349579
* Googletest exportAbseil Team2021-04-161-2/+2
| | | | | | Fix -Wconversion issues on Fuchsia PiperOrigin-RevId: 368520510
* Googletest exportAbseil Team2021-04-081-3/+3
| | | | | | | This is part of a soft transition over to having ZX_INFO_PROCESS populate a new struct. See fxbug.dev/30751 for more details. PiperOrigin-RevId: 367083068
* Googletest exportAbseil Team2021-02-261-1/+1
| | | | | | Update gtest doc link PiperOrigin-RevId: 359622286
* Googletest exportAbseil Team2020-12-101-6/+4
| | | | | | | | | Remove ZX_WAIT_ASYNC_ONCE flag It is deprecated and will soon be removed in fuchsia source. It's currently defined as 0 and references should be changed to 0. PiperOrigin-RevId: 346787585
* Googletest exportdmauro2020-09-301-1/+2
| | | | | | Fix undefined pointer comparison PiperOrigin-RevId: 334436975
* Fix warning maybe-uninitializedrefs/pull/3024/headtbarbier2020-09-241-2/+2
|
* Merge pull request #2895 from lantw44:wip/lantw/Avoid-using-environ-on-FreeBSDvslashg2020-08-241-21/+8
|\ | | | | | | PiperOrigin-RevId: 327799934
| * Avoid using environ on FreeBSDrefs/pull/2895/headTing-Wei Lan2020-06-131-21/+8
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | WebKit passes -Wl,--no-undefined to the compiler when linking shared libraries. This is usually a good practice, but it causes gtest to fail to link because of the use of environ. FreeBSD puts environ symbol in crt1.o instead of libc.so, so the linker is unable to find environ when linking a shared library. Fortunately, there is an easy way to fix it. Since the only use of environ in gtest is to pass it to execve, we can simply replace execve with execv to avoid the need of environ. execv is usually a simple wrapper around execve, so it should be safe to use. This problem was found and reported more than three years ago. The same fix is already committed to WebKit and we don't see any problem reports caused by the change. https://bugs.webkit.org/show_bug.cgi?id=138420 https://trac.webkit.org/changeset/194501/webkit https://bugs.webkit.org/show_bug.cgi?id=208409 https://trac.webkit.org/changeset/257691/webkit https://groups.google.com/forum/#!topic/googletestframework/wrrMj_fmXMc
* | Googletest exportAbseil Team2020-06-261-0/+5
|/ | | | | | Make sure sanitizers do not tamper with the stack here in StackLowerThanAddress(). PiperOrigin-RevId: 318082465
* Googletest exportAbseil Team2019-11-081-1/+1
| | | | | | | | | | | | | | | | | | | | | Clone+exec death test allocates a single page of stack to run chdir + exec on. This is not enough when gtest is built with ASan and run on particular hardware. With ASan on x86_64, ExecDeathTestChildMain has frame size of 1728 bytes. Call to chdir() in ExecDeathTestChildMain ends up in _dl_runtime_resolve_xsavec, which attempts to save register state on the stack; according to cpuid(0xd) XSAVE register save area size is 2568 on my machine. This results in something like this in all death tests: Result: died but not with expected error. ... [ DEATH ] AddressSanitizer:DEADLYSIGNAL [ DEATH ] ================================================================= [ DEATH ] ==178637==ERROR: AddressSanitizer: stack-overflow on address ... PiperOrigin-RevId: 278709790
* restore mistakenly removed iffs in their explicit formrefs/pull/2387/headKrystian Kuzniarek2019-08-201-4/+4
| | | | | Due to confusion arisen from "iff" standing for "if and only if", this commit uses the latter.
* fix typosrefs/pull/2356/headKrystian Kuzniarek2019-07-301-1/+1
|
* Googletest exportAbseil Team2019-07-161-24/+34
| | | | | | | | | [Fuchsia] Update exception APIs used by death test. Migrates to the new channel-based exception APIs as the port APIs are deprecated and will be removed. PiperOrigin-RevId: 258175830
* Googletest exportAbseil Team2019-06-051-1/+1
| | | | | | fdio_pipe_half is now the same as fdio_pipe_half2. We can switch back to the cleaner name. PiperOrigin-RevId: 251633832
* Merge pull request #2170 from ngie-eign:issue-2146-ver2Gennadiy Civil2019-04-181-3/+4
|\ | | | | | | PiperOrigin-RevId: 244069956
| * clang: fix `-Wsign-conversion` errorsEnji Cooper2019-04-061-3/+4
| | | | | | | | | | | | | | | | | | | | | | Cast some values as their unsigned equivalents or `size_t` to match the parameter type used for the template object under test. Also, provide UInt32 equivalent delegate methods for some callers (with int-equivalents for backwards compatibility). This closes #2146. Signed-off-by: Enji Cooper <yaneurabeya@gmail.com>
* | Googletest exportAbseil Team2019-04-161-1/+1
| | | | | | | | | | | | [googletest] Fix death test condition. PiperOrigin-RevId: 243742424
* | Googletest exportAbseil Team2019-04-161-2/+6
|/ | | | | | | | | Migrate ZX_WAIT_ASYNC_REPEATING to ZX_WAIT_ASYNC_ONCE ZX_WAIT_ASYNC_REPEATING is deprecated so convert code to use ZX_WAIT_ASYNC_ONCE instead. PiperOrigin-RevId: 243707147
* Googletest exportAbseil Team2019-04-051-5/+5
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | [fdio] Improve fdio_pipe_half signature, step 3. The return value on fdio_pipe_half conflated two things: the error code on failure (as a zx_status_t) or a file descriptor on success. This technically worked, because they're both ints, the error code was always negative, and the file descriptor always positive. However, the stated return type of zx_status_t was misleading. This changes the signature such that it always returns an actual zx_status_t, and the file descriptor is returned through a pointer argument. Also remove the last argument, since it was always given the same value. This needs to be done as a soft transition because it's called from the Dart runtime, from googletest, and from Crashpad, and Crashpad and Chromium both depend on googletest on Fuchsia. The steps are as follows: 1) Add fdio_pipe_half2. 2) Update Dart to use fdio_pipe_half2. 3) Update googletest to use fdio_pipe_half2. 4) Roll updated googletest into Chronium. 5) Update Crashpad to use fdio_pipe_half2 and roll updated googletest into it. 6) Update fdio_pipe_half to match fdio_pipe_half2. 7) Update Dart to use fdio_pipe_half again. 8) Update googletest to use fdio_pipe_half again. 9) Roll updated googletest into Chronium. 10) Update Crashpad to use fdio_pipe_half again and roll updated googletest into it. 11) Remove fdio_pipe_half2. This is step 3. PiperOrigin-RevId: 241957137
* Googletest exportAbseil Team2019-04-011-0/+4
| | | | | | | | | | | | | | | Add HWASan annotations. These mirror existing ASan annotations. HWASan uses memory (address) tagging to detect memory errors: https://clang.llvm.org/docs/HardwareAssistedAddressSanitizerDesign.html It inserts a random tag in the MSB of heap and stack allocation addresses. This tag dominates pointer comparison in StackGrowsDown(), making the result non-deterministic, and entirely unrelated to the actual stack growth direction. The function attribute disables this behavior. The annotations in gtest-printers are there because the printers are used to basically dump memory. The sanitizers may have ideas why this memory should not be accessed, and that is counter productive. In particular, the test may access only part of an array, but in case of a test failure gtest will dump the entire array which may contain uninitialized bytes - that's what SANITIZE_MEMORY annotation is for. There are similar reasons for ADDRESS and THREAD annotations. HWADDRESS in its current implementation can not cause issues there, I believe, but it falls under the same umbrella of tools whose checking should not apply to test printers because it is not the code under test. PiperOrigin-RevId: 241379822
* Googletest exportAbseil Team2019-02-201-6/+4
| | | | | | | | Update gtest-death-test to use new Fuchsia API Fuchsia has renamed this API and removed the need for several parameters. We now use the newer, simpler API. PiperOrigin-RevId: 234617715
* Googletest exportmisterg2019-01-031-9/+9
| | | | | | TestCase->TestSuite refactoring PiperOrigin-RevId: 227702164
* Googletest exportmisterg2019-01-021-4/+0
| | | | | | Internal Change PiperOrigin-RevId: 227575279
* Googletest exportmisterg2018-12-131-1/+1
| | | | | | Internal Change PiperOrigin-RevId: 225231727
* Googletest exportAbseil Team2018-12-031-6/+7
| | | | | | Applied fixes for ClangTidy modernize-use-override and modernize-use-using. PiperOrigin-RevId: 223800219
* Googletest exportdurandal2018-11-291-45/+46
| | | | | | Accept gmock matchers in EXPECT_EXIT and friends to allow matches other than simple regex matches on death output. PiperOrigin-RevId: 223035409
* Googletest exportmisterg2018-11-201-1/+1
| | | | | | Internal Change PiperOrigin-RevId: 222123106
generated by cgit v0.12 at 2025-04-03 03:45:02 (GMT)