Make the comment indicate more strongly that this behavior
is Darwin-specific and it is not a bug for other platforms to behave
differently.
Details
- Reviewers
labath emaste krytarowski zturner
Diff Detail
Event Timeline
I don't know... Since the test is not annotated, I guess it somehow makes this work, but I haven't been able to find the code that makes it happen.
The problem with this test is that the behavior it prescribes is not compatible with applications that handle SIGSEGV themselves. People have complained about that, including on macos (see D89315). If we were able to tell that the application will not actually handle the SEGV (or other signal), then displaying the process as "crashed" would actually be a good signal to the user. But I don't know of a reasonable way to check whether injecting a signal will cause the app to exit. The situation is probably the same on windows, as it also allows apps to handle their own exceptions (unless we're actually checking whether the application will handle it, which I doubt) , but noone probably noticed it yet...
@zturner, could you tell us what is the expected behavior on Windows? Is it the same as Darwin (i.e. as expected by this test), or do you consider it incidental and would prefer skipping the test on Windows too?
Getting this off my queue. I think the change is fine, but I can also live with the original comment.