New issue
Advanced search Search tips
Note: Color blocks (like or ) mean that a user may not be available. Tooltip shows the reason.

Issue 771387 link

Starred by 3 users

Issue metadata

Status: Untriaged
Owner: ----
Cc:
Components:
EstimatedDays: ----
NextAction: ----
OS: Linux , Android , Windows , Chrome , Mac , Fuchsia
Pri: 3
Type: Bug

Blocking:
issue 776134



Sign in to add a comment

Provide stack traces from ASSERT failures in tests.

Project Member Reported by isherman@chromium.org, Oct 3 2017

Issue description

What steps will reproduce the problem?
1. Write a test with a failing ASSERTion, especially in a helper function.
2. Run the test.

What is the expected result?
  Be able to easily understand the cause of the failure. A stack trace would be helpful.

What happens instead of that?
  No stack trace, which leads to hard-to-understand failures when the assertion is in a helper function.

Developers will sometimes fall back to (D)CHECKs to get stack traces instead.
 

Comment 1 by sczs@chromium.org, Oct 4 2017

Labels: -OS-iOS
Cc: baxley@chromium.org
Blocking: 776134

Sign in to add a comment